On Monday 24 December 2007 10:18 am, Ed Leafe wrote:
> On Dec 24, 2007, at 1:04 PM, Adrian Klaver wrote:
> > Its not a problem with understanding the client-server model. I am
> > also
> > learning to use the python ORM Storm (https://
> > storm.canonical.com/), which by
> > the way is the first one I understand, after failed attempts at
> > SqlAlchemy
> > and SqlObjects. It is not three tier like Dabo, but does have a
> > similar
> > db-->obj layout. To help here is an obj class from Storm
>
> Be very careful in trying to match an ORM approach to the Dabo
> approach. They may have superficial similarities, but they are quite
> different in practice. Example: creating a new EmployeeBizobj doesn't
> create a new Employee record, but would do so in an ORM.
>
> -- Ed Leafe
Yes and no. Storm uses the concept of data stores. So in the code I showed the
data store is sqlite_store=Store(sqlite). If I do :
sqlite_store.find(EmployeeBasic,employee_id=1)
I will get back an instance of EmployeeBasic where employee_id=1 should it
exist.
If I create an instance :
emp_2=EmployeeBasic('init_values')
then I get a new record, but at that point it only exists in memory. In order
to change the data store I have to:
sqlite_store.add(emp_2)
sqlite_store.commit()
At least from my point of view not all that different.
--
Adrian Klaver
[EMAIL PROTECTED]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
