now i could able to run "Ant init" sucessfully, but the "NOT NULL" problem still exists, hence it is showing error while i tried to add user, role etc.
-----Original Message----- From: Christine Keim [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 26, 2002 6:39 PM To: Turbine Users List Subject: Re: Turbine errors in DB2 now, some updates, cause i also have some troubles running tdk 2.1 with db2 > > Error 1: > > While adding constains it showing error like "Length exceeding 18 > > characters" i changed the turbine_schema.xml changing all DB-Table-Names to something very short. I alse changed org.apache.turbine.util.db.map.TurbineMapBuilder.java where all the table names are defined as string. I had to change the table names in the files under WEB-INF\build\bin\torque\templates\sql\security too. There i also deleted the /* statements, u were right, they are causing problems for DB2. Though, i personally find all this a huge hack and i would prefer a better solution. anyone has one? Another problem occurs when sql is generated for the constraints. i had to delete "USING INDEX" and it worked. > > Error 3: > > No Valid driver Well, after the ruckus with my UnsatisfiedLinkError (see other mail) i moved the jar to the ant/lib directory and i also copied one to tdk/lib-directory. it now "ant init"s fine for me. there is still another problem though. ERROR 4: the torque-generated sql-files have all columns defined as NOT NULL, though they are declared as required="false" in the schema. u can see this easily on the table turbine_user which has the email as NOT NULL field in the sql-file but in the xml-definition there's no required attribute at all (also if u add required="false" the behavior is still the same). That means that the file WEB-INF\build\bin\torque\templates\sql\security\default-roles-perms.vm still failes because of a NOT NULL-Exception. This is in my humble opinion a Torque bug - am i wrong? Is there maybe a fix for it available? bye, Christine -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.371 / Virus Database: 206 - Release Date: 6/13/02 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.371 / Virus Database: 206 - Release Date: 6/13/02 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
