On Mon, 2002-02-25 at 04:57, Juli�n H wrote:
> Thanks all who responded so quickly with such detailed helpful information 
> to what now is clear is a fairly fundamental concept... I'm preparing a 
> 'Torque in 5 minutes' that outlines the basic concepts including this one in 
> very clear, succinct language.

Why don't you help with the Tutorial? I would prefer to see any starter
material be place in there.
 
> My problem specifically Bill was that I was getting caught up with that the 
> Torque and SQL schemas are defined -backwards- as far as I'm concerned. If 
> you want to find what collections, say 'Author' has, the schema defines them 
> in the collections -themselves- i.e. Book says 'I want Author to have a 
> bunch of me'.
> 
> Sure this is how SQL works, but did Torque have to work like this as well? 
> Anyway, moot point now. And the tutorial didn't explicitly talk about this 
> relationship, that it's then arranged in the 'proper' order with Author 
> having a method getBooks(). I think this would be helpful; this inversion 
> for non-DB hackers is a bit weird.
> 
> cheers all!
> Julian.
> 
> 
> >From: "Bill Schneider" <[EMAIL PROTECTED]>
> >Reply-To: "Turbine Users List" <[EMAIL PROTECTED]>
> >To: "Turbine Users List" <[EMAIL PROTECTED]>
> >Subject: Re: Torque and 1:n mapping: examples?
> >Date: Sun, 24 Feb 2002 19:38:51 -0500
> >
> >Hi Juli�n:
> >
> >You get Torque to generate Java code to support 1..n relations by 
> >specifying
> >foreign-key constraints in your schema, just as you would if you were
> >writing the SQL data model directly.
> 
> 
> 
> _________________________________________________________________
> Con MSN Hotmail s�mese al servicio de correo electr�nico m�s grande del 
> mundo. http://www.hotmail.com/ES
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]

http://tambora.zenplex.org


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to