Norbert,
I am not sure what you are looking for.... I have turbine running quite
well with MS SQLServer 2000. There where quite a few tweaks that I had to
make to have it all run well.. As far as the "database adapter", I don't
think I used it because I used a JDBC:ODBC bridge... The ant init job
creates all the proper tables for you, including the TURBINE_ tables. The
only thing is that the TURBINE tables require the ID_TABLE table...
Here are my notes that I put together trying to 1) Get basic turbine
running, 2) get the ant sql2xml task to work with DDL exported from
enterprise manager..! I think this would help other poeple who search the
mail archive.
Now I have all 120 tables in my DB modeled in the OM!
Eric Pugh
things to do to make Torque and Turbine work with MS SQL Server 2000 using
JDBC:ODBC
1) Create an ODBC conenction. Make sure that the Use Ansi Nulls paddings
and warning is unchecked.
??2) Change unique.vm for mssql to have the id code
in file
\webapps\newapp\WEB-INF\build\bin\torque\templates\sql\base\mssql\unique.vm
remove the last blank line!
3) In the share\conf\database directory I added a file called "mssql".
These are my contents:
# Set's global values so all builds inherit these setting for MS Sql Server
-dep
database.adaptor = DBMSSQL
database.driver=sun.jdbc.odbc.JdbcOdbcDriver
database.url=jdbc:odbc:MyODBCConnection
database.default.username=myusername
database.default.password=mypassword
4) Check the \share\conf\TurbineResources.properties file. The properties
should read:
database.default.driver=sun.jdbc.odbc.JdbcOdbcDriver
database.default.url=jdbc:odbc:MyODBCCOnnection
database.default.username=myusername
database.default.password=mypassword
database.adaptor=DBMSSQ
database.adaptor.DBMSSQ=sun.jdbc.odbc.JdbcOdbcDriver
5) Change the file share\sample\conf\project-schema.xml to have the table
definition:
<table name="RDF" idMethod="idbroker">
6) A good email:
http://www.mail-archive.com/[email protected]/msg02056.html
7) Now, if you want to use Torque with MS SQL columns that have
autoincrementing primary key identity columns, then it seems that you need
to tweak your project-schema.xml file to say:
<table name="TEMPLATE" idMethod="none">
<column name="TEMPLATE_ID" required="true" autoIncrement="false"
primaryKey="true" type="INTEGER"/>
Using idMethod="native" doesn't seem to work... none is deprecated however
so native should work at some point!
8) Default login name is turbine/turbine!
Torque Notes
1) Remove all [ and ] and .dbo in schema.sql file
2) in the schema.xml file, make sure you set your package to where the OM
will reside!
-----Original Message-----
From: Norbert Rieger [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 17, 2001 4:22 AM
To: [EMAIL PROTECTED]
Subject: Turbine Support For MS SQLServer
I've seen that Turbine supports several databases like oracle, mysql,
sybase, postgres, etc.
Unfortunately we have to support MS's SQLServer database. Therefore I'm
looking for an (real) implementation for the database adaptor (class
DBMSSQL).
I've seen the HowTo, but if somebody has done this job....
So, if there is someone with this implementation (eventually including
the database scripts for the TURBINE_ tables) please let me know.
Thanks in advance
Norbert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
