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 AutoTranslate
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 above mentioned
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
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 when
a
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 (see above) who
has access to the same
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
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 sure
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
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 mapper
On 10/5/07, Gustavo Schneider [EMAIL PROTECTED] wrote:
Hi all SQLAlchemists,
Hi,
[...]
The code:
code
table1 = Table('table1', metadata,
Column('id', types.Integer, Sequence('table1_id_seq'), primary_key=True)
)
/code
When using postgresql you can have only this code and it
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
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
12 matches
Mail list logo
