Shaun Campbell wrote:
>
> First of all can Torque be made to work with pre-existing databases?
Yes. I am sure there are some things that will not work, but we can't
cover everything at least until we know what "everything" is. Here's an
example of something that probably will not work out of the bag:
A sequence is defined for id generation and there is a trigger (or some
other db specific way) to get the next id on an insert. However, there
is no sql defined for retrieving the id that was used.
> Do you
> just have to generate the schema xml file by hand?
There is an sql to xml converter. It works well for MySQL, can't
speculate on other db's.
> Also, with updates to
> the database do you just have to maintain the xml schema file manually? I
> don't suppose there's anyway to make the changes in the xml file and then
> impose them on the database, thereby, making the xml file the master.
You are correct in saying the xml file cannot be the master and it will
generate sql "fragments" to keep the db up-to-date. (It does not
generate "alter table" commands.)
>
> Secondly, if I don't want to add to or modify the existing database in any
> way can I get Torque to work off a separate database?
>
> Finally, regarding the Turbine tables for security etc, as in the second
> point, can they also be installed in a separate turbine database?
They can be installed as a separate db. The primary difficulty is then
associating a user with other objects. This will likely require some
custom code. And actually the last sentence could apply to many
circumstances.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
