Re: [sqlalchemy] Using SQL_CALC_FOUND_ROWS

I answered this for someone some time ago, assuming FOUND_ROWS() is local to a MySQL session (note this is not the same thing as a SQLAlchemy session though typically these map in a 1-1 fashion) there should be no issue, as long as you are using each connection in just one application thread

[sqlalchemy] Using SQL_CALC_FOUND_ROWS

Hi All, I want to use SQL_CALC_FOUND_ROWS with my select query and use a following SELECT FOUND_ROWS() to get the total count in sqlalchemy. But how do I make sure *SELECT FOUND_ROWS()* returns the correct cached value in the case of *concurrent* queries of *select SQL_CALC_FOUND_ROWS* happen?

Re: [sqlalchemy] Create Table DDL options before "("

I've added you to the "contributors" group so you should have access now. On 05/23/2016 12:45 PM, Mark Sandan wrote: No worries, I'll put up a reference to the PR and gerrit proposal in case anybody wants to chime in. The change is proposed in git PR #275

Re: [sqlalchemy] Create Table DDL options before "("

No worries, I'll put up a reference to the PR and gerrit proposal in case anybody wants to chime in. The change is proposed in git PR #275 and in gerrit (which I'm still getting used too). On Sunday, May

Re: [sqlalchemy] zero_indexes broken for 2d-arrays?

Thanks Mike. That fixed it!. On Monday, May 23, 2016 at 10:18:15 AM UTC-4, Mike Bayer wrote: > > > > On 05/23/2016 10:12 AM, Brian Cherinka wrote: > > > > Hi, > > > > It seems like the ARRAY option zero_indexes=True is broken for > > 2-dimensional arrays. Is this a bug that is fixed in

Re: [sqlalchemy] zero_indexes broken for 2d-arrays?

On 05/23/2016 10:12 AM, Brian Cherinka wrote: Hi, It seems like the ARRAY option zero_indexes=True is broken for 2-dimensional arrays. Is this a bug that is fixed in 1.1? I'm actually using the subclass ARRAY_D as a fix for the __getitem__ indexing. It works for 1-D arrays. if you're

[sqlalchemy] zero_indexes broken for 2d-arrays?

Hi, It seems like the ARRAY option zero_indexes=True is broken for 2-dimensional arrays. Is this a bug that is fixed in 1.1? I'm actually using the subclass ARRAY_D as a fix for the __getitem__ indexing. It works for 1-D arrays. *1-D array* wave = Column(ARRAY_D(Float,

Re: [sqlalchemy] Calculated relationships

I see that it's not on the web GUI either. Yes, that's a google bug. In https://support.google.com/groups/answer/2466386?hl=en , I click the "post and always allow future messages from author" button, same button I've been clicking for like eight years.Googling (heh) for any reported