Re: Is this a transaction use case?

DavidA wrote: > The identity value is set in the new instance once you call save so you > can simply do this: > > p = Property(sq_feet=2300, ...) > p.save() # now p.id is set > > a = Ad(property=p, ...) > a.save() > > The equivalent of the @@Identity trick is handled during

Re: Is this a transaction use case?

[EMAIL PROTECTED] wrote: > Hi all, > > i have the following scenario for a real-estate search engine: > > "Ad" table where i define the properties of the ad such as created_on, > expires_on, user_id and is related with a 1-1 FK to the "Property" > table which defines stuff such as sq_feet,

Is this a transaction use case?

Hi all, i have the following scenario for a real-estate search engine: "Ad" table where i define the properties of the ad such as created_on, expires_on, user_id and is related with a 1-1 FK to the "Property" table which defines stuff such as sq_feet, district_id etc... I'd like to keep them