Oops, obviously I made a mess of my program when pasting it into the
web form. Of course, there was a foreign key right from the beginning.
A whole line including a parenthesis and a comma dropped out:
referer = Table(referer, metadata,
Column(id, Integer, primary_key=True),
just to add an option,
sometimes i solve such flat-namespace-collisions by adding inner level
of syntax in argument values + parsing them, e.g. for command line
strings:
myapp mainarg1=v1 mainarg2=v2 sqlite='arg1:val1,arg2:val2'.
this is somewhat ugly too, and is even uglier to extend to more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi mike,
i have installed the 0.3.9 from svn, and now it's returning the primary
key values of the last inserted record, as documented, even if those are
not numeric.
thanks a lot!
though i'm on a well packaged debian system, i have a lib
On Jul 9, 2007, at 8:55 AM, alex bodnaru wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi mike,
i have installed the 0.3.9 from svn, and now it's returning the
primary
key values of the last inserted record, as documented, even if
those are
not numeric.
thanks a lot!
could i make the sqlalchemy subdirectory updateable by svn, or
should i
re-egg the updated package after every significant change?
setuptools has a notion of PYTHONPATH thats not compatible with
Python's notion of itits usually easiest to python setup.py on
whatever version
Sorry about the sporadic posts, I'm travelling
if we are going whole hog with query strings (basically we're talking
about adding pool options mostly), a comprehensive solution needs to
be added in DefaultEngineStrategy.
All that sounds fine, if Paul is still interested, I'll work with him on
Thanks
On Jul 9, 7:44 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Jul 9, 2007, at 3:40 AM, mc wrote:
I have a followup question:
You posted above a function for retrieving the values by using another
select query.
The fact is that regardless of the differences between SQLalchemy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi all,
i'm using sa 0.3.9 from svn for the new last_inserted_ids functionality.
after upgrading from official 0.3.8 i have encountered the following
problem:
since i'm calling a select statement using whereclause with bindparams,
its execution
I'm still having problems with this (sorry about the huge delay, I got
side-tracked for a while). After creating parent/child/attribute
table rows, I get one of two errors when I try to print
parent.attributes:
If I use the column name id in my child table I get this error:
I'm not sure whether I understody your posting correctly. Now I've
checked out revision 2867 and nothing has changed, that is, I still
get the same exceptions.
Best regards
Klaus
On Jul 9, 9:44 am, klaus [EMAIL PROTECTED] wrote:
Oops, obviously I made a mess of my program when pasting it
On Jul 9, 2007, at 9:37 PM, BruceC wrote:
Hi all, I am using Pylons, SQLAlchemy (via PYODBC) to connect
through to an MSSQL database. In particular, I have been trying to use
Christoph Haas' alternative Paginator (http://workaround.org/pylons/
paginator/paginator.html) webhelper, which
11 matches
Mail list logo