On 20 Nov 2000, (Daniel L. Rall) wrote:
> Jason van Zyl <[EMAIL PROTECTED]> writes:
>
> > The following SQL files are now in CVS:
> >
> > turbine-mysql.sql
> > turbine-postgres.sql
> > turbine-db2.sql
> > turbine-sybase.sql
> > turbine-hypersonic.sql
> > turbine-oracle.sql
> >
> > These files are in the src/sql directory. There are more then
> > likely problems with all so I if any can spare a moment
> > to look at any of the files it would be appreciated.
>
> Once the SQL scripts are in working order, what do you think about
> removing them from CVS and generating them as part of the TDK creation
> process?
Probably don't want to force people to use the TDK, even though
that is the method we promote. We should probably leave copies
of the SQL in CVS. The same idea applies to the peers generated
by Torque. We should probably start generating the Turbine peers.
So we have to come up with some system for generating a Turbine
distribution if all we keep in CVS is the Torque schema.
As part of Turbine distribution build, the SQL for the supported
DBs, and the turbine peers would be packaged up. The same sort
of procedure could be used for the TDK. I've been thinking
about it but haven't come up with a plan yet :-(
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
