Re: [sqlalchemy] 0.6b1 and pymssql

would probably consider pyodbc is I was stuck with MSSQL. -- Yannick Gingras http://ygingras.net http://confoo.ca -- track coordinator http://montrealpython.org -- lead organizer signature.asc Description: This is a digitally signed message part.

Re: [sqlalchemy] 0.6b1 and pymssql

and we moved to MySQL. For the record, the segfault occurred in PyTuple_SET_ITEM() on line 2186 of mssqldbmodule.c. I don't have an MSSQL instance handy right now so it's hard to give details. -- Yannick Gingras http://ygingras.net http://confoo.ca -- track coordinator http://montrealpython.org

Re: [sqlalchemy] Working with temp tables on Postgres

for other criteria order by rank -- Yannick Gingras http://ygingras.net http://confoo.ca -- track coordinator http://montrealpython.org -- lead organizer signature.asc Description: This is a digitally signed message part.

[sqlalchemy] Working with temp tables on Postgres

problems? -- Yannick Gingras http://ygingras.net http://confoo.ca -- track coordinator http://montrealpython.org -- lead organizer signature.asc Description: This is a digitally signed message part.

Re: [sqlalchemy] Working with temp tables on Postgres

it. Thank again for all the infos. -- Yannick Gingras http://ygingras.net http://confoo.ca -- track coordinator http://montrealpython.org -- lead organizer signature.asc Description: This is a digitally signed message part.

[sqlalchemy] Looking for a schema / database migration tool

: http://groups.google.com/group/migrate-users/browse_thread/thread/f95ac435aa27280c Are there any other tool that could do the job? How hard would it be to modify sqlalchemy-migrate to work with dependencies instead of sequential version numbers? Best regards, -- Yannick Gingras http

[sqlalchemy] Slow session.commit()?

) -- -- Yannick Gingras http://ygingras.net http://confoo.ca -- track coordinator http://montrealpython.org -- lead organizer signature.asc Description: This is a digitally signed message part.

[sqlalchemy] License of the example files

Greetings Alchemists, I plan to base a chunk of my code on one of the examples in sqlalchemy/examples. I just want to make sure that those are free to use. SQLAlchemy is licenced under the X11 (MIT) license. Is it also the case for the examples? -- Yannick Gingras http://ygingras.net http

[sqlalchemy] Duck-typing style of relations

=...) However, it's hard to extend when you need a new kind of objects that has addresses. Is there a better solution? -- Yannick Gingras http://ygingras.net signature.asc Description: This is a digitally signed message part.

[sqlalchemy] Re: Duck-typing style of relations

(company_id IS NULL) (person_id IS NULL), but it is easy to extend to 2 FK columns. Thats a very nice solution indeed. Thanks! -- Yannick Gingras http://ygingras.net signature.asc Description: This is a digitally signed message part.

[sqlalchemy] Re: Portable Enum Columns

. Thanks for the info. -- Yannick Gingras http://ygingras.net signature.asc Description: This is a digitally signed message part.

[sqlalchemy] Portable Enum Columns

on the wiki: http://www.sqlalchemy.org/trac/wiki/UsageRecipes/Enum Is there another way to do it? Something that would be portable and to both MySQL and Postgres would be great. Regards, -- Yannick Gingras http://ygingras.net signature.asc Description: This is a digitally signed message part.

[sqlalchemy] ConFoo.ca call for speakers

a talk to PyCon [2], which is also running its call for speakers as I write this. Share the word! [1]: http://confoo.ca/en/cfp [2]: http://us.pycon.org/2010/about/ -- Yannick Gingras http://ygingras.net signature.asc Description: This is a digitally signed message part.

[sqlalchemy] Re: Problems with pyodbc on RHEL 64

for 1.0 implied it was more or less a total rewrite; I stayed away for the time being. Last question: are on 32 bit or on 64 bit? Our dev boxen are in 32 bit and there a lot of stuff that goes fine on them until we push the code to the staging server that runs on 64 bit. -- Yannick Gingras http

[sqlalchemy] Re: Problems with pyodbc on RHEL 64

are mostly using Alchemy for the connection pooling; we have a few mapped objects but most of our queries are still hand written and we don't want to convert them all to the SQL abstraction layer provided by Alchemy right now. Any advice on using Pymssql with Alchemy? -- Yannick Gingras http

[sqlalchemy] Re: Problems with pyodbc on RHEL 64

0.8.0 or the 1.0.x branch? They somewhat change the API in 1.0.x to make it more compliant with the python db api 2.0 and I assume that it has impacts on the Alchemy support. -- Yannick Gingras http://ygingras.net signature.asc Description: This is a digitally signed message part.

[sqlalchemy] Problems with pyodbc on RHEL 64

. What do you guys recommend? Running the experimental 0.6 Alchemy branch? -- Yannick Gingras http://ygingras.net/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email

[sqlalchemy] Comparable ColumnDefaults for shema diffing

monkey patching? -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL

[sqlalchemy] Re: Comparable ColumnDefaults for shema diffing

effect that I didn't foresee, I will implement the comparator in the diffing library. It the same way, what do you think about __eq__() for types? This is False: types.Integer(10) == types.Integer(10) which was unexpected to say the least but there might be a good reason for it. -- Yannick

[sqlalchemy] Re: Schema and database migration: how to diff?

of its own? With the `changeset` parts of sqlalchemy_migration, we could generate most of the upgrade script from the computed diff. Unless you already do that and I missed that part somehow. -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message

[sqlalchemy] Schema and database migration: how to diff?

? If not, what gotchas should I know about before I try my hand at such a framework? -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy

[sqlalchemy] Re: Pre-commit hooks

, None): instance._pre_update() return EXT_CONTINUE -- It works great. Thanks for the pointers. -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

[sqlalchemy] Re: Pre-commit hooks

of your approach. I just refactored my implementation. Thanks! -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com

[sqlalchemy] Re: Connecting to an MS SQL server ?

-4a47fe38beac67d9d03e49c4975cfc3dd165fa31 My obdb.ini looks like [JDED] Driver = TDS Trace = No Server = 192.168.33.53 Port= 1433 and my alchemy connection string is mssql://user:pass@/?dsn=JDEDscope_identity=1 -- Yannick Gingras

[sqlalchemy] Re: Query filtering like isinstance()

. Is it possible to retried it if I have only the class object? This is not a big problem since I can use Item.__name__ as the polymorphic_identity. -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

[sqlalchemy] Pre-commit hooks

the test in it. -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL

[sqlalchemy] Re: Query filtering like isinstance()

).polymorphic_identity should work It does. Thanks! -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe

[sqlalchemy] Re: Query objects and empty slices

. this will be easy to fix in 0.5 since slices will no longer be generative, so we'll just return an empty iterator. ticket 1035 in trac. Sounds good. Keep up the good work. -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you

[sqlalchemy] Query objects and empty slices

? -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more

[sqlalchemy] Re: Query objects and empty slices

preference goes for returning an empty list without emitting SQL. -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com

[sqlalchemy] Re: Aliasing automatic joins with relation.any()

= :item_ids_ref_id_1' is overcorrelated; returned no 'from' clauses Could I do it with raw exists()? -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send

[sqlalchemy] Re: Aliasing automatic joins with relation.any()

. It also works on 0.4.5. Can you make sure you're on 0.4.5 and then create a test case for me ? I was with 0.4.4. It works perfecly fine with 0.4.5 and reset_joinpoint(). Thanks! -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you

[sqlalchemy] Aliasing automatic joins with relation.any()

.ref_id = :item_ids_ref_id_1' is overcorrelated; returned no 'from' clauses I had the same error with the first query before I aliased it so I assume that it's an aliasing problem. How can I alias the ref_ids.any() clause? -- Yannick Gingras

[sqlalchemy] Re: ORM as a view

), status_rule_last=relation(OrderRule, It would be nice if the example could illustrate this subtlety. Otherwise, I love it. Thanks! -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy

[sqlalchemy] ORM as a view

() would only fetch rows with col_a == foo and col_b == bar. I know how to do that for a field of the object with relation(..., primary_join=...) How would I do that at the object level? -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because

[sqlalchemy] Read-only Sessions

, transactional=True, bind=config['pylons.g'].sa_engine)) So the session object is reused all over the place and overwriting one of its methods is not a good idea. What would be my best option to implement readonly mode? -- Yannick Gingras

[sqlalchemy] Re: Read-only Sessions

you recommend for a per-session read-only mode? -- Yannick Gingras --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from