Sorry of this is a repost -- I sent it once before joining the list. I
don't think it went through though...
---
Hello,
I've started using sqlalchemy a few weeks ago for a recent project.
Right now I've version locked to 0.1.5 unless there's a compelling
reason for me to move past that.
The
OK, itll go into the 0.2 series since id rather not be supporting
multiple syntaxes (i.e. the old one is going to go)
On Apr 17, 2006, at 1:49 AM, William K. Volkman wrote:
On Mon, 2006-04-17 at 01:23 -0400, Michael Bayer wrote:
On Apr 17, 2006, at 12:42 AM, William K. Volkman wrote:
Hell
On Mon, 2006-04-17 at 01:23 -0400, Michael Bayer wrote:
> On Apr 17, 2006, at 12:42 AM, William K. Volkman wrote:
>
> > Hello,
> >
> > I just getting started evaluating SQL Alchemy.
> >
> > Not recalling the documentation very clearly I wrote the DB URL
> > as I expected it to work:
> >
> > engine
On Apr 17, 2006, at 12:42 AM, William K. Volkman wrote:
Hello,
I just getting started evaluating SQL Alchemy.
Not recalling the documentation very clearly I wrote the DB URL
as I expected it to work:
engine = create_engine('postgres://scott:[EMAIL PROTECTED]:5049/test')
if you can find me
Hello,
I just getting started evaluating SQL Alchemy.
Not recalling the documentation very clearly I wrote the DB URL
as I expected it to work:
engine = create_engine('postgres://scott:[EMAIL PROTECTED]:5049/test')
although I got an engine object, trying e.get_default_schema_name()
gives me: ps
I wrote:
Well, it wasn't the r1256 issue. Your example runs fine, but my code
still ends up adding the yearly alias to the FROM of the outer query -
obviously, my simple examples 'are not the examples I was looking for' -
further investigation required.
Ok, found the problem, I was using
On Apr 16, 2006, at 6:33 PM, I wrote:
I'll check out further what the problem at my end is (one possibility
I've just discovered is that the machine I'm running this on is on an
older rev of SA (r1256) - one of the perils of being able to use
python setup.py -develop in any checked out r
yah i dont like that -develop flag very much, not sure why its so
popular. Ben makes it default in the myghty trunk but its not my
preference.
On Apr 16, 2006, at 6:33 PM, Robert Leftwich wrote:
Michael Bayer wrote:
this example gives you the output you want. not sure why yours
isnt w
Michael Bayer wrote:
this example gives you the output you want. not sure why yours isnt
working:
Thanks a heap for taking the time to work up this example
I'll check out further what the problem at my end is (one possibility I've just
discovered is that the machine I'm running th
robert -
this example gives you the output you want. not sure why yours isnt
working:
from sqlalchemy import *
daily = table('daily',
column('id'),
column('code'),
column('date'),
)
yearly = table('yearly',
column('id'),
column('date'),
)
yearly_2 = yearly.alia
Michael Bayer wrote:
try using the flag "correlate=False" in the Select which you want to be
fully self-contained.
Unfortunately, I need it to be correlated (it is relative to the current daily
date), it just needs its own FROM statement.
(also post the full code, since I think using th
robert -
try using the flag "correlate=False" in the Select which you want to
be fully self-contained.
(also post the full code, since I think using the alias for the
"yearly" table should be working also)
On Apr 15, 2006, at 9:43 PM, Robert Leftwich wrote:
I'm trying to setup a complica
Many thanks Robert :) I found some examples of chained joins later
while using the manual as a sleep aid
but your explanation is clearer.
Cheers!
--Peter
At 04:19 16.4.06, Robert Leftwich wrote:
Peter L. Buschman wrote:
Apologies since this seems like a basic question, but what is the
bes
hello again,
setting
echo=True
in create_engine solved my problem - i get
[2006-04-16 09:39:52,694] [engine]: SELECT branche.id, branche.name
FROM branche
WHERE branche.name LIKE %(branche_name)s ORDER BY branche.name
[2006-04-16 09:39:52,696] [engine]: {'branche_name': '%Spedition%'}
on the
14 matches
Mail list logo
