Hey,
a workaround i've used is is to manually set primary key to being a
composite of all columns if the table has no actual primary key. however,
this will mean that sqlalch ignores any duplicate rows, which you may not
want.
hp.
On Thu, Jul 1, 2010 at 7:41 PM, sandro dentella san...@e-den.it
On Jul 6, 2010, at 4:18 AM, Harry Percival wrote:
Hi,
I've got an error which occurs in ironpython but not in cpython. can anyone
replicate? See attached. I'm using IPY 2.6.
string:1: DeprecationWarning: object.__init__() takes no parameters for
type _keyed_weakref
string:1:
Hi Michael,
thanks for replying - the reason I attached a zipfile is because sqlite
isn't supported natively on ironpython, so I've had to include the source
and a dll for it. So, if you did have time to open it up and take a peek,
I'd very much appreciate it.
Alternatively, how can I run the
I'd like to use the postgresql OVER constructions, as seen at
http://www.postgresql.org/docs/8.4/static/tutorial-window.html.
Some of the things I tried:
# gives an extra comma, which is fail.
print select([s.ts,PARTITION OVER( ts )])
SELECT summary.ts, PARTITION OVER( ts )
FROM summary
#
Hello list -
Another month (more or less), another release.SQLAlchemy 0.6.2 is out.
Highlights of this release:
- one showstopper was fixed. Firebird support was busted for 0.6.1, repaired
that.
- one semi-showstopper, though we've all been putting up with it for a long
time, was
Does SA support this syntax?
http://www.postgresql.org/docs/9.0/static/queries-with.html
Thanks,
Mike
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this
this is the current status of that:
http://groups.google.com/group/sqlalchemy/browse_thread/thread/c20a4f380e277af/fb179a515bf48868
WITH and OVER seem to be the upcoming things we'll have to work on (PG, MSSQL,
DB2 support WITH). Oracle makes WITH difficult.Its also getting to be
time to
Thanks for the fast reply. This is exciting. Both WITH and OVER are
two things that I look forward to then.
On Jul 6, 4:31 pm, Michael Bayer mike...@zzzcomputing.com wrote:
this is the current status of that:
http://groups.google.com/group/sqlalchemy/browse_thread/thread/c20a4f...
WITH and
Hi, I was wondering what method might be used (assuming it's possible)
to redefine a column's attribute type after the mapping has already
been made? Specifically I have the following scenario:
from sqlalchemy import *
from sqlalchemy.orm import mapper
metadata = MetaData()
orders = Table(