>> John McNally wrote:
>> Why is ExecuteOdbcTurbineSchema.java in the sql directory?
Access doesnt have an inbuilt tool to run an sql script.
ExecuteOdbcSchema.java is a tool to do that, which is why I submitted it,
otherwise the db schema has to be generated by hand inside the Access db
which is laborious. So its fuctionality is only for generating schemas from
sql scripts for ODBC.
>Very good! I left that in there as a test to see if anyone's paying
>attention.
>Why we're on the topic of the sql directory, do we really
>need to keep an Access db there (Turbine-AccessY2k.mdb)? We could save
>about 250k on the download size without it.
The reason I sent it in was that not all of the Turbine db can be mimicked
from scripts in Access, the defaults I couldnt get to work through SQL. The
other thing it is a pain to generate anyway, so it is easier for someone
just to attach a DSN to Turbine-AccessY2K.mdb and then configure their
TurbineResources.properties. I have created a ready to go HypersonicSQL
database as well which is about 160 Kb.
It is no big deal to me if everyone wants it be cut. I did it mainly to help
those in win32 who are getting their feet wet with Turbine.
>(Self-proclaimed Access DB hater!)
Like it all things it has its place and area of use. Where Access fufills
the role required of a project Im involved in, I have no irrational base
against it being used.
Cameron Riley
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
