> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 27, 2001 1:00 PM > To: [EMAIL PROTECTED] > Subject: Re: Torque and <filesets> > > > On 9/27/01 3:49 PM, "Fedor Karpelevitch" > <[EMAIL PROTECTED]> > wrote: > > > > > > We are trying to solve slightly different problems, I guess. > > I am talking about a case when some schema is an integral > part of a bigger > > schema. An example is turbine schema which is a part of a > turbine app's > > schema. In this case, I guess, it would be valuable to be > able to "include" > > turbine schema into app schema, so they are considered to > be the same db. > > This would not let you provide a wrong FK from your table > to TURBINE_USER > > and such and would not require you to do any cut-and-paste > which is never > > good. This also reflects dependencies correctly - app > schema depends on > > turbine schema. So when you do an uptodate check you would > be able to (and > > should to be correct) also walk down the deps - id app > schema is updated it > > needs to be regenerated, if turbine schema is updated - > both need to be > > regenerated. > > What you are trying to do is to process several independent > schemas in one > > shot. It may have it's valid applications, but it's a > different case... > > Yes, but I don't think your method of including would be a problem if > filesets were introduced. Do you mind the additional of filesets?
no. > > > fedor > > > > -- > > jvz. > > Jason van Zyl > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
