Thanks,
Seems you're making progress. The instructions for CodeSwitcher are also in
the Guide document.
The main tests to run are those in the org.hsqldb.test directory, especially
TestSelf.java. Some of these tests require JDK > 1.1, so you can exclude
them.
For client/server, you should modify TestBase to use a network connection
(you need to change the value of a flag in the source code).
When you run a command against one of the databases in the Server, it will
not affect other databases. You are probably using the wrong connection in
this test.
Fred
----- Original Message -----
From: "Carfield Yim" <[EMAIL PROTECTED]>
To: <hsqldb-developers@lists.sourceforge.net>
Sent: 10 March 2005 10:52
Subject: Re: [Hsqldb-developers] Fwd: Small developer tasks for 1.8.0
> We don't want any change to the way different versions are handled.
>
> Regarding committing to CVS, we only allow it when someone is responsible
> for an area of code. Otherwise a lot of extra and unnecessary management
> is
> required.
>
ok
> See the Guide on CodeSwitcher for the pre-processor comments. The
> supported
> switches are in the build.xml file.
>
You mean the javadoc? Actually I've read that before but I can't
figure out how it working... fortunately the whole source code is
there and I get that from the file "jdbcConnection.java"
> In theory, you should be able to use the JDBC client built with a
> different
> JDK, but it must be the same revision of HSQLDB 1.8.0.
>
> If you cannot connect at all, please recheck that everyting is the same
> version and report.
The client have problem is download from hsqldb website, after I
replace it with the same jar that just compile, it work, all testcase
press. And I've try some alter table statement that work also.
I find only one project, if the hsql server start with 2 database
setup. The server always think that one command is applied to both
server. e.g.
1) I run alter table add column command on one database, success; Then
run it at other database, it say the column already exist.
2) I shutdown one database, ok; Then try to shutdown the other one, it
reply connection close, but in fact the server still running.
Here is the list of SQL command I haven't test, which I guess minor:
ALTER INDEX
ALTER SEQUENCE
ALTER USER
CALL
CHECKPOINT
CREATE ALIAS
CREATE TRIGGER
CREATE USER
CREATE VIEW
DROP INDEX
DROP SEQUENCE
DROP TRIGGER
DROP USER
DROP VIEW
REVOKE
SAVEPOINT
SET IGNORECASE
SET LOGSIZE
SET PASSWORD
SET PROPERTY
SET REFERENTIAL INTEGRITY
SET SCRIPTFORMAT
SET TABLE INDEX
SET TABLE READONLY
SET TABLE SOURCE
SET WRITE DELAY
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
hsqldb-developers mailing list
hsqldb-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
hsqldb-developers mailing list
hsqldb-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
