Re: [sqlalchemy] sqlalchemy 0.6 and mock strategy produces different SQL for postgres

On Tuesday 05 January 2010 19:26:56 Michael Bayer wrote: On Jan 5, 2010, at 11:35 AM, Diez B. Roggisch wrote: Hi, we have a utility-script schemautil that allows us to re-create our DB based on the metadata of SA, or simply dump the generated SQL for manual inspection - the latter is

Re: [sqlalchemy] sqlalchemy 0.6 and mock strategy produces different SQL for postgres

Diez B. Roggisch wrote: On Tuesday 05 January 2010 19:26:56 Michael Bayer wrote: On Jan 5, 2010, at 11:35 AM, Diez B. Roggisch wrote: Hi, we have a utility-script schemautil that allows us to re-create our DB based on the metadata of SA, or simply dump the generated SQL for manual

Re: [sqlalchemy] sqlalchemy 0.6 and mock strategy produces different SQL for postgres

Diez B. Roggisch wrote: On Tuesday 05 January 2010 19:26:56 Michael Bayer wrote: On Jan 5, 2010, at 11:35 AM, Diez B. Roggisch wrote: Hi, we have a utility-script schemautil that allows us to re-create our DB based on the metadata of SA, or simply dump the generated SQL for manual

[sqlalchemy] sqlalchemy 0.6 and mock strategy produces different SQL for postgres

Hi, we have a utility-script schemautil that allows us to re-create our DB based on the metadata of SA, or simply dump the generated SQL for manual inspection - the latter is used when one writes migration scripts. Now we noticed a strange behavior: the generated SQL isn't working for

Re: [sqlalchemy] sqlalchemy 0.6 and mock strategy produces different SQL for postgres

On Jan 5, 2010, at 11:35 AM, Diez B. Roggisch wrote: Hi, we have a utility-script schemautil that allows us to re-create our DB based on the metadata of SA, or simply dump the generated SQL for manual inspection - the latter is used when one writes migration scripts. Now we noticed