Turns out that SA 0.5 had been installed in virtualenv, but the system
version was SA 0.4.3 (from Ubuntu). I uninstalled the system version,
and reinstalled with SA 0.5.2. That fixed the problem.
Thanks!
Edgar
On Mar 17, 3:30 pm, Jonathan Vanasco wrote:
> add() is the name in SA.5 for save()
add() is the name in SA.5 for save() in SA.4
"session.add() replaces session.save(), session.update(),
session.save_or_update(). - the session.add(someitem) and
session.add_all([list of items]) methods replace save(), update(), and
save_or_update(). Those methods will remain deprecated throughout
> On Mar 17, 1:08 pm, Wyatt Baldwin wrote:
>
> > On Mar 17, 9:00 am, edgarsmolow wrote:
>
> > > I'm trying to get a foothold in Pylons 0.9.7 with SQLAlchemy 0.5, but
> > > running into a problem when testing model functionality. In
> > > particular, there's a Person object which is supposed to
import sqlalchemy as sa
import w2t.model as model
import w2t.model.meta as meta
session = meta.Session()
wilma = model.Person('Wilma','Flintstone')
wilma.acct_no = 'SOMEACCOUNTNUMBER'
wilma.gender = 'F'
session.add(wilma)
meta.Session.commit()
Since neither meta.Session or session have an add me
On Mar 17, 9:00 am, edgarsmolow wrote:
> I'm trying to get a foothold in Pylons 0.9.7 with SQLAlchemy 0.5, but
> running into a problem when testing model functionality. In
> particular, there's a Person object which is supposed to be stored in
> the persons table. Here's test code snippet:
>
I'm trying to get a foothold in Pylons 0.9.7 with SQLAlchemy 0.5, but
running into a problem when testing model functionality. In
particular, there's a Person object which is supposed to be stored in
the persons table. Here's test code snippet:
wilma = model.Person('Wilma','Flintstone')
wilma.
