On 4/19/07, Michael Bayer [EMAIL PROTECTED] wrote:
On Apr 19, 2007, at 9:39 AM, Gaetan de Menten wrote:
By the way, lately I've been wishing SQLAlchemy would add a column
(and possibly its table) automatically to the select clause if I do an
order by a column which is not in the
I have this piece of code which I came across accidentally:
page = 0
limit = '1'
# note that one of the above values is a string, and the other a 0
data = ATable.select(a_table.c.id.in_(*aIDs), limit=limit, offset=(page*limit))
Note the * on strings which is resulting in ''
Now this query
On Friday 20 April 2007 16:59:55 Michael Bayer wrote:
On Apr 20, 2007, at 5:00 AM, Ram Yalamanchili wrote:
I have this piece of code which I came across accidentally:
page = 0
limit = '1'
# note that one of the above values is a string, and the other a
0 data =
On Apr 20, 2007, at 5:00 AM, Ram Yalamanchili wrote:
I have this piece of code which I came across accidentally:
page = 0
limit = '1'
# note that one of the above values is a string, and the other a 0
data = ATable.select(a_table.c.id.in_(*aIDs), limit=limit, offset=
(page*limit))
Hi wfpearson,
On Apr 18, 1:21 pm, wfpearson [EMAIL PROTECTED] wrote:
[snip full description of the problem]
I've tried the following method:
surgery = session.query(Surgery).select_by(dictation=None)[0]
I'm pretty new to all of this myself, but maybe try using clause
elements in yout
I noticed current release information is now available on the
SQLAlchemy homepage! Good job!
Greg
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
On 4/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Friday 20 April 2007 16:59:55 Michael Bayer wrote:
On Apr 20, 2007, at 5:00 AM, Ram Yalamanchili wrote:
I have this piece of code which I came across accidentally:
page = 0
limit = '1'
# note that one of the above
Murphy's law strikes again. As soon as I sent the email, I finally
noticed that I wasn't passing my table into my outputs_mapper after
staring at it for an hour...
Sorry for the spam!
--
Jonathan LaCour
http://cleverdevil.org
--~--~-~--~~~---~--~~
You received
First thing I'm doing is rewriting the model and mapper without
Elixir. I'm not sure if that was causing the issue or not. This is so
frustrating because SQLAlchemy's documentation is so thorough I
thought I would be able to solve it on my own.
On Apr 20, 2:35 pm, desmaj [EMAIL PROTECTED] wrote:
On Apr 20, 2007, at 5:21 PM, Ram Yalamanchili wrote:
Passing a string in limit or offset does work (atoi done internally i
think). Thats the reason I thought offset='' doesn't make sense.
Shouldn't there atleast be a better error than trying to figure what
is wrong with the sql statement?
On Apr 20, 2007, at 11:14 PM, Paul Kippes wrote:
I had been using an order_by with the AssociationProxy since 0.3.4.
In 0.3.6, this has been broken or else no longer supported. Since
this is an extension, it has no unit tests (is this the norm?)
extensions do have unit tests in some
11 matches
Mail list logo
