Michael Bayer wrote:
jose soares wrote:
Michael Bayer wrote:
jo wrote:
I was using heavily the column_prefix and my code is full of it, as
in:
mapper(Anagrafica,
tbl['anagrafica'],
column_prefix = 'anagrafica_',
extension=History(),
properties = {
'comune' : relation( Comune, primaryjoin =
tbl['anagrafica'].c.id_comune == tbl['comune'].c.id ),
'nazione' : relation( Nazione, primaryjoin =
tbl['anagrafica'].c.cod_cittadinanza ==
tbl['nazione'].c.codic...
'comune_nascita' : relation( Comune, primaryjoin =
tbl['anagrafica'].c.id_comune_nascita == tbl['comune'].c.id),
'nazione_nascita': relation( Nazione, primaryjoin =
tbl['anagrafica'].c.cod_nazione_nascita ==
tbl['nazione'].c.co...
'professione' : relation( Professione ),
'titolo_studio' : relation( TitoloStudio ),
}
)
column_prefix remains available. That above code is compatible with
0.6.
I tried upgrade from 0.3 to 0.4 and if I remember well, there wasn't
column_prefix in 0.4.
Are you suggest me to migrate directly from 0.3 to 0.6 instead of a
gradual migration?
if it were me I'd certainly go straight to 0.6. I'd be curious to know
what kinds of code patterns you think would be difficult to migrate (I
haven't used 0.3 in years obviously).
Well, I need to accommodate SQLAlchemy with an old versione of
Turbogears, and it is not so easy,
anyway, I think I'll get another try.
I hope you can help me to solve some possible trouble. :-)
j
--
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 group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
