Re: [sqlalchemy] twophase error sqlalchemy

2013-06-26 Thread Pau Tallada
Ok, that was my fault. I was calling rollback() on a sqla.orm.session, instead of calling transaction.abort() Although the documentation only forbids calling commit, it does not say anything about rolling back an individual session :( Thanks! Pau. 2013/6/25 Michael Bayer

Re: [sqlalchemy] HSTORE serialize/de-serialize incorrectly handles backslashes

2013-06-26 Thread Ryan Kelly
On Tue, Jun 06/25/13, 2013 at 02:47:18PM -0400, Michael Bayer wrote: On Jun 25, 2013, at 2:13 PM, Ryan Kelly rpkell...@gmail.com wrote: There are also some other parsing problems that I consider to be corner cases and broken as implemented in PostgreSQL, such as:

[sqlalchemy] Unable to store datetime.datetime.max using SQLAlchemy==0.8.1 with the mysql-python==1.2.4 driver

2013-06-26 Thread Pelle Almquist
Hi, not sure if I should post this issue here or if its a mysql-python one but perhaps someone with better knowledge can help me figure that out? A more pretty print version of this issue is available here:

Re: [sqlalchemy] HSTORE serialize/de-serialize incorrectly handles backslashes

2013-06-26 Thread Michael Bayer
On Jun 26, 2013, at 6:57 AM, Ryan Kelly rpkell...@gmail.com wrote: On Tue, Jun 06/25/13, 2013 at 02:47:18PM -0400, Michael Bayer wrote: On Jun 25, 2013, at 2:13 PM, Ryan Kelly rpkell...@gmail.com wrote: There are also some other parsing problems that I consider to be corner cases and

Re: [sqlalchemy] Unable to store datetime.datetime.max using SQLAlchemy==0.8.1 with the mysql-python==1.2.4 driver

2013-06-26 Thread Michael Bayer
On Jun 26, 2013, at 10:18 AM, Pelle Almquist pe...@wrapp.com wrote: Hi, not sure if I should post this issue here or if its a mysql-python one but perhaps someone with better knowledge can help me figure that out? A more pretty print version of this issue is available here:

[sqlalchemy] Declarative Sequences

2013-06-26 Thread Mat Mathews
Apologies if I'm posting a question to this group incorrectly or with bad etiquette. I've been reading the emails from this group for a few years and now have a question myself. I am automating the creation of our models and business objects by reading a schema definition from YAML. We use

Re: [sqlalchemy] Declarative Sequences

2013-06-26 Thread Michael Bayer
On Jun 26, 2013, at 12:02 PM, Mat Mathews m...@miga.me wrote: I would like to do something like this: class User(object): id = Column(Integer, Sequence('user_id_seq', start=1), primary_key=True) This does work, and emits the CREATE SEQUENCE, but does not set the owned table

Re: [sqlalchemy] Declarative Sequences

2013-06-26 Thread Mat Mathews
Thanks for the quick reply. If I modify the name of the sequence in the test, it reproduces what I have experienced. When I check the details on the sequence in postgres, there is no table owner or column specified by the sequence 'test_user_id_seq'.. and I would expect to see both tables

Re: [sqlalchemy] Declarative Sequences

2013-06-26 Thread Michael Bayer
On Jun 26, 2013, at 1:26 PM, Mat Mathews m...@miga.me wrote: Thanks for the quick reply. If I modify the name of the sequence in the test, it reproduces what I have experienced. When I check the details on the sequence in postgres, there is no table owner or column specified by the

Re: [sqlalchemy] Declarative Sequences

2013-06-26 Thread Mat Mathews
That absolutely solves my issue. I had a serious suspicion I was missing something, and it was to look at the Column options, not just the Sequence. Thanks a ton. On Jun 26, 2013, at 7:44 PM, Michael Bayer mike...@zzzcomputing.com wrote: On Jun 26, 2013, at 1:26 PM, Mat Mathews