I tested on Friday with the rc1 build, using JSQLConnect, and got 0 failures, 1 error, which I was told was not important.
Today, testing with the rc2 build, and with the columns modifed to be NOT NULL as specified earlier, I get 0 failures, 4 errors. I have no clue if these are important or not. Bonnie MacKellar -----Original Message----- From: BURT, RANDALL (CONTRACTOR) [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 5:01 PM To: OJB Users List Subject: RE: MSSQL server - error in ojbtest-schema.xml Some issues with the JSQLConnect driver: 1. Due to network restrictions, I suppose, I was getting 403 errors using the ant task to download the driver. I grabbed it manually without incident, and commented out the ant call. 2. I am actually getting *more* JUnit failures/errors with this driver, though I concede it may be due to the changes I mentioned below in the ojbtest-schema.xml? 3. With the money the PHB's are already throwing at MS licensing, I am loath to try and work another ($4000+ for us, if I read their pricing correctly) purchase into the budget... -----Original Message----- From: Matthew Baird [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 3:25 PM To: OJB Users List Subject: RE: MSSQL server - error in ojbtest-schema.xml I don't have any issues with MSSQL, but the driver always makes a difference. When people ask me I recommend the JSQLConnect #1 and Opta2000 #2. Bother are great drivers. -----Original Message----- From: BURT, RANDALL (CONTRACTOR) [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 1:25 PM To: OJB Users List Subject: RE: MSSQL server - error in ojbtest-schema.xml I'll give it a shot. Truth to tell, *I* wouldn't use MSSQL server at all, but this is a port of an app we "inherited", so we're kinda stuck... :( -----Original Message----- From: Matthew Baird [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 3:20 PM To: OJB Users List Subject: RE: MSSQL server - error in ojbtest-schema.xml if you are worried about using OJB, I'd be more worried about using the MS Driver. Switch over and use the JSQLConnect profile and the build will automatically download the jsqlconnect driver which is much better. -----Original Message----- From: BURT, RANDALL (CONTRACTOR) [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 1:20 PM To: OJB Users List Subject: RE: MSSQL server - error in ojbtest-schema.xml Glad I could help. I can sympathize with your trepidation about using OJB in a large project. Seems I've been taking one step forward and two steps back for the last few days. I like what it is and what it does, though, and I can't see hacking a persistence service for the projects I have lined up would be very cost-effective... As for those JUnit errors I mentioned before, anyone getting anything like this (from tests-broker.txt): [org.apache.ojb.broker.accesslayer.JdbcAccessImpl] ERROR: SQLException during the execution of the query (SELECT count(A0.*) FROM Artikel A0 WHERE A0.Kategorie_Nr = ? ) (for a org.apache.ojb.broker.Article): [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Line 1: Incorrect syntax near '*'. [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Line 1: Incorrect syntax near '*'. I hacked the test a bit so I could see the query that bombed (pre-preparation), but it doesn't look like it should fail to me. I'm down to my last three errors (broker tests) and one failure (ODMG tests) and would like to start testing with "real" data in my application environment. -----Original Message----- From: Bonnie MacKellar [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 3:09 PM To: OJB Users List Subject: RE: MSSQL server - error in ojbtest-schema.xml Thanks for this post. I was also getting this today (using JTurbo). Bonnie MacKellar -----Original Message----- From: BURT, RANDALL (CONTRACTOR) [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 3:05 PM To: OJB Users List Subject: MSSQL server - error in ojbtest-schema.xml Don't know if I should submit a bug report on this or not, but when I tried to run the prepare-testdb target using MSSQL server 2000 (MS's JDBC Driver), I would get the following error: [torque-insert-sql] Executing file: C:\java\utils\db-ojb-1.0.rc2\target\src\sql\ojbtest-schema.sql [torque-insert-sql] Failed to execute: /* ---------------------------------------------------------------------- */ [torque-insert-sql] /* REF_REPOSITORY_FK */ /* ---------------------------------------------------------------------- */ IF EXISTS (SELECT 1 ( ... ) [torque-insert-sql] java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Cannot define PRIMARY KEY constraint on nullable column in table 'REF_REPOSITORY_FK'. This was fixed by changing the REF_REPOSITORY_FK table description in ${OJB_HOME}\src\schema\ojbtest-schema.xml to make the required fields not null: <table name="REF_REPOSITORY_FK"> <column name="REP_ID" required="true" primaryKey="true" type="INTEGER"/> <column name="REF_FK" required="true" type="INTEGER" primaryKey="true"/> <column name="REFA_FK" required="true" type="INTEGER" primaryKey="true"/> <column name="REFB_FK" required="true" type="INTEGER" primaryKey="true"/> <column name="NAME" type="VARCHAR" size="100"/> </table> The tables now build correctly, though I am still tracking down some failed JUnit tests. Hope this helps somebody... --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
