[sqlalchemy] Re: patch for mssql odbc

2008-04-08 Thread Florent Aide
On Tue, Apr 8, 2008 at 7:02 PM, Rick Morrison <[EMAIL PROTECTED]> wrote: > I'll reply here rather than on the ticket as I'm unable to stay logged into > Trac from here (dual TCP/IP address problem). > I see no objection as long as we can document it somewhere to say it will impact the AutoTransla

[sqlalchemy] patch for mssql odbc

2008-04-08 Thread Florent Aide
Hi all, I have just posted a patch for the MSSQL_odbc dialect. The ticket number is #1005. It enables MSSQL odbc users to make sure their odbc layer will not try to translate textual data (in some cases it is not desirable to do so). Florent Aide

[sqlalchemy] Re: unicode support for MSSQL

2007-11-25 Thread Florent Aide
On Nov 25, 2007 6:24 PM, Paul Johnston <[EMAIL PROTECTED]> wrote: > > Hi Florent, > > Just realised we'd gone quiet on this thread... > > >humm What bothers me is that I already get this comportement when > >running my query program from a Linux host (using pyodbc same version) > >but need the abo

[sqlalchemy] spam

2007-11-14 Thread Florent Aide
Hi moderators, Could we ban this Riaz M. from sending any more emails to this group? He also tried to send a lot of spam in TurboGears group and I moderated and banned him again there. Regards, Florent. --~--~-~--~~~---~--~~ You received this message because you

[sqlalchemy] Re: Firebird engine - support for embedded version

2007-11-12 Thread Florent Aide
On Nov 12, 2007 12:57 PM, Werner F. Bruhin <[EMAIL PROTECTED]> wrote: > > Which means firebird.py does not need to be patched, however I still see > > the same problem that the process hangs. > > > > > As the version of FB is 2.1beta I wondered if maybe there is an issue > with it, so I just did a

[sqlalchemy] Re: unicode support for MSSQL

2007-11-10 Thread Florent Aide
On Nov 8, 2007 7:30 PM, Paul Johnston <[EMAIL PROTECTED]> wrote: > > Hi, > > >I have isolated the problem a little bit more: my column is defined in > >the MSSQL server as a user defined type which is based on VARCHAR. > > > > > Ok, so in this case you'd like SA to return a python unicode object w

[sqlalchemy] Re: unicode support for MSSQL

2007-11-08 Thread Florent Aide
Hi Paul and others, I attached a new patch to the ticket (#839). It corrects the comportements I have and I now receive unicode objects in all cases: either when I declared String or Unicode as the column type and whatever the type of my columns in MSSQL (varchar based or nvarchar based) I thin

[sqlalchemy] Re: unicode support for MSSQL

2007-11-08 Thread Florent Aide
On Nov 8, 2007 1:36 PM, Florent Aide <[EMAIL PROTECTED]> wrote: [...] > My patch then "works" because in fact the object that come back from > sql server is a binary string encoded using the aforementioned > 'codepage'. I had contact with Christophe de Vienne

[sqlalchemy] Re: unicode support for MSSQL

2007-11-08 Thread Florent Aide
On Nov 5, 2007 6:50 PM, Paul Johnston <[EMAIL PROTECTED]> wrote: [...] > Are your strings VARCHAR or NVARCHAR? > > If they're NVARCHAR, all this will just work as-is with SA and MSSQL - > are you having any specific problems? > > If they're VARCHAR, then we need to think some more. I'm still not

[sqlalchemy] Re: unicode support for MSSQL

2007-11-04 Thread Florent Aide
On Nov 3, 2007 12:01 PM, Paul Johnston <[EMAIL PROTECTED]> wrote: > > Florent, > > >I just added ticket #839 to the trac and attached a patch that enables > >unicode conversion for MSSQL dialects. > >I tested it with pyodbc but it should work the same with the other dialects. > > > > > What's the

[sqlalchemy] unicode support for MSSQL

2007-10-30 Thread Florent Aide
Hi Mike, Hi all, Our conversation yesterday night on IRC gave me ideas :) I just added ticket #839 to the trac and attached a patch that enables unicode conversion for MSSQL dialects. I tested it with pyodbc but it should work the same with the other dialects. Best regards, Florent Aide

[sqlalchemy] Re: TurboGears: best practices for SELECTing

2007-10-11 Thread Florent Aide
On 10/11/07, James Brady <[EMAIL PROTECTED]> wrote: > > Did you call assign_mapper on Ownership? > > [...] > > However, I'm using the identity framework (part of TurboGears) which > unfortunately doesn't play nicely with assign_mapper... shame! > If you use SA 0.3.10 I would advise you to use m

[sqlalchemy] Re: Problems with Sequence on PostgreSQL.

2007-10-05 Thread Florent Aide
On 10/5/07, Gustavo Schneider <[EMAIL PROTECTED]> wrote: > > Hi all SQLAlchemists, Hi, [...] > > The code: > > table1 = Table('table1', metadata, > Column('id', types.Integer, Sequence('table1_id_seq'), primary_key=True) > ) > When using postgresql you can have only this code and i

[sqlalchemy] Re: interface error with Decimal("0") in where clause

2007-08-24 Thread Florent Aide
How would you do something like this then: session.query.(LedgerLine).query(LedgerLine.base_amount.between(decimal1, decimal2)) the between() won't work since sqlite won't be able to compare your pickled amounts. Pickling cannot be an option in all cases particularly when you are storing amount

[sqlalchemy] Re: interface error with Decimal("0") in where clause

2007-08-24 Thread Florent Aide
Hi, As far as I know, sqlite does not allow you to store decimal objects, only floats. Which really is not the same. If you really need decimals (ie: accounting books anyone ?) then you should consider using firebird which is the only other database engine supported by SA that is embeddable in a