Hi,
Thanks for the help. Looks like I'm still stuck though.
Use the latest SVN version of SA 0.4, where I've fixed this issue.
You'll need to do something like:
svn checkout http://svn.sqlalchemy.org/sqlalchemy/trunk sqlalchemy
cd sqlalchemy
setup.py develop
Paul
Am Montag, 15. Oktober 2007 20:14 schrieb Michael Bayer:
HI Hermann -
table/column naming looks like this:
mytable = Table('sometablename', metadata,
Column('colname', Integer, key='someothername')
)
access the column:
mytable.c.someothername
so above, we access the real
Hi Florent,
On Oct 11, 1:01 pm, Florent Aide [EMAIL PROTECTED] wrote:
On 10/11/07, James Brady [EMAIL PROTECTED] wrote:
Did you call assign_mapper on Ownership?
[...]
However, I'm using the identity framework (part of TurboGears) which
unfortunately doesn't play nicely with
SQLAlchemy generates wrong SELECTs for classes that are mapped to
select expressions. Consider the following example:
from sqlalchemy import *
metadata = MetaData(..., echo=True)
table = Table(test, metadata,
Column(id, Integer, primary_key=True),
Column(data,
The following used to work in SQLAlchemy 0.3:
from sqlalchemy import *
from sqlalchemy.orm import *
metadata = MetaData(...)
metadata.bind.echo=True
table = Table(test, metadata,
Column(id, Integer, primary_key=True),
Column(active, Boolean))
table.create()
Maybe I should add that this bug appears under PostgreSQL and persists
in version 0.4.
On 16 Okt., 15:50, klaus [EMAIL PROTECTED] wrote:
SQLAlchemy generates wrong SELECTs for classes that are mapped to
select expressions. Consider the following example:
from sqlalchemy import *
metadata =
On Oct 16, 2007, at 10:53 AM, klaus wrote:
Maybe I should add that this bug appears under PostgreSQL and persists
in version 0.4.
fixes forthcoming
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy
On Oct 16, 2007, at 10:45 AM, klaus wrote:
The only thing that I could find out about the reason is that in
engine/base.py (1290)
context.column_labels
contains the wrong entries. It should contain something like
{..., 'table_column': 'table_column', ...}.
In the case above,
On Oct 16, 2007, at 1:30 PM, [EMAIL PROTECTED] wrote:
Hi everybody!
I've got a schema with a combined 1:n:1 + m:n relation.
In detail, I have the entities user and event and the relation
participation.
That leads to 1:n user-participation, n:1 participation-event, and
m:n user-event:
Having problems all day connecting and tried various apps just in
case... is there anyway I could get someone to zip and host this
really quick?
Error * PROPFIND request failed on '/sqlalchemy/trunk' PROPFIND of '/
sqlalchemy/trunk': could not connect to server (http://
svn.sqlalchemy.org)
Hi,
I'm trying to determine a way to append a LIMIT to an update()
object.
Is the solution a correlated update on the same table with the LIMIT
on the select() object?
Cheers,
Jim
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Yes, that would be the only thing that has a hope of working across database
engines. LIMIT with UPDATE is MySQL-only AFAIK.
For SA, joins in updates can be tricky, so the correlated query would best
be a IN() or EXISTS() query that has the limit you want. To get a
deterministic set of records
12 matches
Mail list logo
