On Thu, Aug 08, 2013 at 01:47:42PM +0400, Oleg Broytman wrote:
> On Thu, Aug 08, 2013 at 09:34:18AM +0200, Gert Burger
> wrote:
> > Oleg Broytman wrote, On 07/08/2013 19:51:
> > > On Wed, Aug 07, 2013 at 11:52:15AM +0200, Gert Burger
> > > wrote:
> > >> Attached is a test case demonstrating th
On Thu, Aug 08, 2013 at 09:34:18AM +0200, Gert Burger
wrote:
> Oleg Broytman wrote, On 07/08/2013 19:51:
> > On Wed, Aug 07, 2013 at 11:52:15AM +0200, Gert Burger
> > wrote:
> >> Attached is a test case demonstrating the issue. Tested with version
> >> 1.5.0b1 and some previous versions.
> >
>
Oleg Broytman wrote, On 07/08/2013 19:51:
> Hi!
>
> On Wed, Aug 07, 2013 at 11:52:15AM +0200, Gert Burger
> wrote:
>> Attached is a test case demonstrating the issue. Tested with version
>> 1.5.0b1 and some previous versions.
>
>Thanks for the report!
>
>> The EnumValidator checks if the v
Hi!
On Wed, Aug 07, 2013 at 11:52:15AM +0200, Gert Burger
wrote:
> Attached is a test case demonstrating the issue. Tested with version
> 1.5.0b1 and some previous versions.
Thanks for the report!
> The EnumValidator checks if the value given is in the list of valid
> enumValues but this al
Hi
Attached is a test case demonstrating the issue. Tested with version
1.5.0b1 and some previous versions.
The EnumValidator checks if the value given is in the list of valid
enumValues but this allows unicode values to match normal string values.
That allows unicode objects into the SQL genera