For sql to xml generation you can use the "sql2xml" target in the build-project file
(TDK 1.1a10). It does a fairly decent job of
generating an xml schema that you can then edit. At least it saves you a lot of typing
:)
I use the xml file as the master, make my changes there, and regenerate the sql schema
and the om with "build-project project-sql"
and "build-project project-om" whenever I change that file.
I have no experience with seperate databases in Turbine so I'll let someone else
answer that one. I just know that it IS possible.
Age
> -----Original Message-----
> First of all can Torque be made to work with pre-existing databases? Do you
> just have to generate the schema xml file by hand? 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.
>
> 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?
>
> Thanks
>
> Shaun Campbell
>
>
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
