from sqlalchemy import *
m= MetaData()
trans =Table( 'trans', m, Column( 'date', Date), )
balance=Table( 'balance', m, Column( 'finaldate', Date), )
b = balance.alias('b')
sprev = select( [ func.max( b.c.finaldate)],
b.c.finaldate < balance.c.finaldate
)
#correlate i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi jerryji,
this database is not normalized.
you may consider switching to:
things(thingid INTEGER, thing_weight etc.)
and
things_translations(thingid INTEGER, thing_name VARCHAR, language CHAR(5))
jerryji wrote:
> Dear Kind Soul,
>
> I am stuck w
Dear Kind Soul,
I am stuck with the following database referential integrity
constraint problem.
I have two tables:
things(thingid INTEGER, thing_name VARCHAR, language CHAR(5))
and
thing_relations(thingid INTEGER, thing_parentid INTEGER)
things hosts items in different languages, e.g.:
things(
On Dec 15, 2007, at 9:34 AM, Vladimir Iliev wrote:
> hi, i hit another dynamic relations related bug. if you remove
> lazy='dynamic' from items mapping there's no problem.
>
OK, I know what this is and it involves making query translation a
little more intelligent. The issue is not really th
Hi!
I'm trying create table in database, but 'default' option isn't using,
when executing 'paster setup-app development.ini' ...
__init.py__
from sqlalchemy import *
from sqlalchemy.databases.mysql import *
from sqlalchemy.ext.assignmapper import assign_mapper
from pylo
hi, i hit another dynamic relations related bug. if you remove
lazy='dynamic' from items mapping there's no problem.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send ema
On Dec 15, 2007, at 12:04 PM, Allen Bierbaum wrote:
>
> The one question I have here though is, how can I make the update()
> call that reattaches it to the foreground session automatically reload
> the entire record from the database (ie. ignore any local
> modifications)? Do I have to call up
Can't you use a BETWEEN or >= and < with two dates?
If your date column is indexed, as it should be if you're using it
frequently in where clauses, the overhead of DATE_FORMAT decreases
substantially.
On Dec 12, 2007 3:43 PM, Adam B <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 11, 10:55 am, "King S
On Dec 13, 2007 12:29 PM, Allen Bierbaum <[EMAIL PROTECTED]> wrote:
> On Dec 13, 2007 10:47 AM, Michael Bayer <[EMAIL PROTECTED]> wrote:
> > On Dec 13, 2007, at 9:55 AM, Allen Bierbaum wrote:
> > >
> > > In my current application I am running a rather expensive query in a
> > > background thread,
seems like you might need an as_scalar() on the select object.
otherwise send an example.
On Dec 15, 2007, at 10:06 AM, svilen wrote:
>
> seems something about .type vs .type_ or similar:
>
> Traceback (most recent call last):
> File "tests/convertertest.py", line 152, in
> test4_balance_tr
seems something about .type vs .type_ or similar:
Traceback (most recent call last):
File "tests/convertertest.py", line 152, in
test4_balance_trans_via_prev_balance_date_subselect
trans.c.date > func.coalesce( sprev,0 )
File "sqlalchemy/sql/expression.py", line 777, in __call__
retu
11 matches
Mail list logo