[sqlalchemy] Re: use_labels =30 vs MAX_LABEL_LENGTH

2007-03-17 Thread jose
Michael Bayer wrote: ideally the truncation should be occuring at the SQL compilation phase so you wouldnt have this problem. i recall that being very complex but i should take a look again to see if theres any major barriers to that. but for now, sure, ive no problem with a module-level

[sqlalchemy] Re: use_labels =30 vs MAX_LABEL_LENGTH

2007-03-17 Thread Jorge Godoy
jose [EMAIL PROTECTED] writes: * PostgreSQL = 64 - 1 This can be changed in compilation time. -- Jorge Godoy [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to

[sqlalchemy] Re: use_labels =30 vs MAX_LABEL_LENGTH

2007-03-17 Thread Michael Bayer
On Mar 17, 3:57 am, jose [EMAIL PROTECTED] wrote: May be you may assign the MAXLENGTH depending on the database, for example: * MySQL = 64 * PostgreSQL = 64 - 1 * Firebird = 31 ? * Oracle = 30 * MS-SQL = 128 well yes thats the whole issue. we are doing the length truncation at the point