Re: ustring compose escaping capability

["Szilard Pfeiffer" <szilard pfeiffer gmail com>]

I hope there will be no misunderstanding if I write it step-by-step:

1. in the glibmm there is an ustring::compose API
2. it is not possible to escaping with this API
3. it would be useful for us (my colleges and me) and maybe for others
4. we have a potential solution (without API incompatibility)
5. with some work i can create a patch for you
6. it would be lovely if you integrated our patch to the glibmm

Do you plan to implement your own solution to the problem?
May I hope you integrate our solution to the glibmm if you find it correct?

regards
Szilard

p.s.:

In this case escaping means string conversion. I think something like the following:

ustring::compose("SELECT * FROM table_name WHERE pub='%1'", "Joe's")

The result of the composition should be "SELECT * FROM table_name WHERE
pub='Joe\'s'", but without escaping it will be "SELECT * FROM
table_name WHERE pub='Joe's'", which is an incorrect SQL command.

On Jan 22, 2008 10:43 PM, Jonathon Jongsma <jonathon quotidian org> wrote:

On 1/22/08, Szilárd Pfeiffer <szilard pfeiffer gmail com> wrote:
> Hi,
>
> I have a question about the ustring::compose API. Is it purposed
> implementation of an escaping extension to the compose API? We have a
> solution for that and we would be happy if you found it useful and it
> was integrated to the glibmm 2.16 or later.
>
> regards
> Szilard

I don't quite understand the question.  Would it be possible to
re-word it somehow?

--
jonner