Re: [sqlalchemy] Percona Server

2015-10-28 Thread Mike Bayer
On 10/28/15 1:45 PM, Sean Harrington wrote: > Has anybody tried to use SQLAlchemy on Percona Server? yes Percona Server is > a "drop-in replacement" for MySQL with InnoDB optimizations -- however > it contains additional INFORMATION_SCHEMA tables, and performance > tables...Want to make sure

[sqlalchemy] Re: Percona Server

2015-10-28 Thread Waldemar Osuch
On Wednesday, October 28, 2015 at 11:45:45 AM UTC-6, Sean Harrington wrote: > > Has anybody tried to use SQLAlchemy on Percona Server? Percona Server is a > "drop-in replacement" for MySQL with InnoDB optimizations -- however it > contains additional INFORMATION_SCHEMA tables, and performance >

[sqlalchemy] Percona Server

2015-10-28 Thread Sean Harrington
Has anybody tried to use SQLAlchemy on Percona Server? Percona Server is a "drop-in replacement" for MySQL with InnoDB optimizations -- however it contains additional INFORMATION_SCHEMA tables, and performance tables...Want to make sure that SQLAlchemy will still sit atop Percona the same way t

Re: [sqlalchemy] Relationships not being set to None when related object is deleted

2015-10-28 Thread Mike Bayer
On 10/28/15 1:26 PM, Chris Wilson wrote: > OK, I hadn't thought of that, it might work but in fact I want to delete > a Cat when it has no Houses left (House -> Cat in this case, with > uselist=True instead of uselist=False as in the example above) and it's > not clear that delete-orphan can reli

Re: [sqlalchemy] Relationships not being set to None when related object is deleted

2015-10-28 Thread Chris Wilson
Hi Michael, Thanks for replying so quickly! On Wednesday, 28 October 2015 15:04:56 UTC, Michael Bayer wrote: > OK, sorry, you've misunderstood the documentation. When it says > "delete", it refers to the *parent* object that refers to the *child*, > that is, the parent is the one that th

Re: [sqlalchemy] TypeDecorator odd behavior

2015-10-28 Thread Uri Okrent
Ah! Thanks so much. I spent the whole morning stepping through this in the debugger trying to understand what was happening. I finally got to this point: When column is JSONDict, > /Library/Python/2.7/site-packages/sqlalchemy/engine/base.py(886) _execute_context() -> if context.compiled: (Pdb

Re: [sqlalchemy] Relationships not being set to None when related object is deleted

2015-10-28 Thread Mike Bayer
On 10/28/15 10:42 AM, Chris Wilson wrote: > Hi all, > > I'm having problems with relationships getting out of sync with the > underlying foreign key properties, and hoping that someone can help. > > It seems from the manual (if I've understood correctly), that deleting > one side of a relations

Re: [sqlalchemy] TypeDecorator odd behavior

2015-10-28 Thread Mike Bayer
On 10/27/15 9:01 PM, Uri Okrent wrote: > Hello, I've created a TypeDecorator for use with postgresql's JSON type, > for the purpose of adapting it to sqlite and it's producing an incorrect > bind parameter when using JSON's column index operation. > > I'm using sqlalchemy 0.9.4 (I haven't been

[sqlalchemy] Relationships not being set to None when related object is deleted

2015-10-28 Thread Chris Wilson
Hi all, I'm having problems with relationships getting out of sync with the underlying foreign key properties, and hoping that someone can help. It seems from the manual (if I've understood correctly), that deleting one side of a relationship should set foreign keys on the other side to NULL/N

[sqlalchemy] Re: TypeDecorator odd behavior

2015-10-28 Thread Uri Okrent
update: tried with 0.9.10 and I see the same behavior On Tuesday, October 27, 2015 at 9:01:55 PM UTC-4, Uri Okrent wrote: > > Hello, I've created a TypeDecorator for use with postgresql's JSON type, > for the purpose of adapting it to sqlite and it's producing an incorrect > bind parameter when