crossdb-developers Mailing List for crossdb - Java - database independent co (Page 3)
Status: Beta
Brought to you by:
prophecyslides
Menu
▾
▴
crossdb-developers — for developers
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(28) |
Jun
(14) |
Jul
(7) |
Aug
(7) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(9) |
Feb
(2) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tr...@th...> - 2002-05-31 03:28:43
|
Kevin, I found an issue with the Abstract classes you proposed. Take the OracleCreateTableQuery for example, look at the execute method. It requires two different create statements, one for the sequence, one for the table. So a getQuery() on this would not work. Travis |
|
From: <tr...@th...> - 2002-05-30 21:01:12
|
I've added the old notion of using a crossdbResultSet to format results when needed for a specific implementation. Ex: getDate should return exactly the same in all cases now (SQL server before retruend the time with the date which was incorrect). Anybody working on an implementation should implement this if needed. If not, you shouldn't need to change anything. Look at SQLServer implementation for example. Travis |
|
From: <tr...@th...> - 2002-05-28 17:37:29
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2716.2200" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff>hey kevin, if you want to start a new cvs branch or module to incorporate your ideas, let me know and give me your sourceforge login. <br> <br> Travis <br> <br> ---- Original Message ---- <br> From: KevinLentle <<a href="mailto:ke...@me...">ke...@me...</a>> <br> Sent: 2002-05-26 <br> To: CrossDB Developers <<a href="mailto:cro...@li...">cro...@li...</a>> <br> Subject: [Crossdb-developers] AbstractAlterTableQuery.java;AbstractCreateTableQuery.java;AbstractTableQuery.j <br> <br> <DIV><FONT size=2>Hi Guys,</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Attached are the source for the abstract classes. As mentioned before I havn't spent a lot of time on this, so far, but should be-able to devote a bit more to it now.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Let me know what you think.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Kev.</FONT></DIV></BODY></HTML> |
|
From: <tr...@th...> - 2002-05-27 22:06:25
|
What do you guys think shoudl be the default, null or not null when creating a table? Travis |
|
From: <tr...@th...> - 2002-05-27 19:39:02
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2716.2200" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff>Interesting concept. <br> <br> I guess if all implementations can work with this kind of framework, then it would be much easier to create an implementation, that's for sure. <br> <br> Anybody else have any comments on this? <br> <br> Travis <br> <br> <br> ---- Original Message ---- <br> From: KevinLentle <<a href="mailto:ke...@me...">ke...@me...</a>> <br> Sent: 2002-05-26 <br> To: CrossDB Developers <<a href="mailto:cro...@li...">cro...@li...</a>> <br> Subject: [Crossdb-developers] AbstractAlterTableQuery.java;AbstractCreateTableQuery.java;AbstractTableQuery.j <br> <br> <DIV><FONT size=2>Hi Guys,</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Attached are the source for the abstract classes. As mentioned before I havn't spent a lot of time on this, so far, but should be-able to devote a bit more to it now.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Let me know what you think.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Kev.</FONT></DIV></BODY></HTML> |
|
From: James S. <jam...@ya...> - 2002-05-24 16:44:29
|
> Ya, that's probably a good idea. KISS = keep it simple stupid. ;-)
>
> So are you thinking:
>
> class ColumnValues {
> java.util.List columnValues;
>
> }
> class ColumnValue {
> String col;
> String value;
> }
>
> Something like that anyways?
Value needs to be an object.
Though I'd be tempted to use a Map for ColumnValues rather than a List of
ColumnValue objecs. Or at least some map-like interface...
public class ColumnValues {
public Iterator getNames();
public Object getValue(String name);
pubilc void setValue(String name, Object value);
public int size();
}
Actually maybe just use a Map?
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|
|
From: <tr...@th...> - 2002-05-24 16:37:07
|
Ya, that's probably a good idea. KISS = keep it simple stupid. ;-)
So are you thinking:
class ColumnValues {
java.util.List columnValues;
}
class ColumnValue {
String col;
String value;
}
Something like that anyways?
The one issue we have to consider as well is that in a WhereCondition, the values could be both columns, a column vs a value, or even value vs value (not sure why you'd want that, but it is allowed).
Right now I have it in the queries as
addWhereCondition("x", WhereCondition.EQUAL_TO, "y");
if you want to compare column vs string, you would use
addWhereString("x", WhereCondition.EQUAL_TO, "y");
then y will be surrounded by single quotes and sql escaped.
Travis
---- Original Message ----
From: James Strachan <jam...@ya...>
Sent: 2002-05-24
To: cro...@li...
Subject: Re: [Crossdb-developers] Query interface problem
From: <tr...@th...>
> Just ran into another issue.
>
> SelectQuery execute() returns ResultSet, the rest return ints.
Maybe we should just have Query, which has an execute() method that returns
a ResultSet then all the other interfaces are Operations which don't return
result sets and can be used polymorphically?
Most of my comments about being more polymorphic were aimed at all the heaps
of methods in InsertQuery, UpdateQuery, DeleteQuery etc that could well be
kept inside common classes like ColumnValues and WhereClause. Right now it
looks a lot of work to implement the insert/update/delete classses.
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Crossdb-developers mailing list
Cro...@li...
https://lists.sourceforge.net/lists/listinfo/crossdb-developers
|
|
From: James S. <jam...@ya...> - 2002-05-24 07:48:55
|
From: <tr...@th...> > Just ran into another issue. > > SelectQuery execute() returns ResultSet, the rest return ints. Maybe we should just have Query, which has an execute() method that returns a ResultSet then all the other interfaces are Operations which don't return result sets and can be used polymorphically? Most of my comments about being more polymorphic were aimed at all the heaps of methods in InsertQuery, UpdateQuery, DeleteQuery etc that could well be kept inside common classes like ColumnValues and WhereClause. Right now it looks a lot of work to implement the insert/update/delete classses. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
|
From: <tr...@th...> - 2002-05-24 05:26:39
|
Just ran into another issue. SelectQuery execute() returns ResultSet, the rest return ints. Travis |
|
From: <tr...@th...> - 2002-05-23 22:38:29
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2716.2200" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff>Good point. <br> <br> Can you send a code sample of what you are talking about so we can see it better? <br> <br> Travis <br> <br> ---- Original Message ---- <br> From: KevinLentle <<a href="mailto:ke...@me...">ke...@me...</a>> <br> Sent: 2002-05-23 <br> To: CrossDB Developers <<a href="mailto:cro...@li...">cro...@li...</a>> <br> Subject: [Crossdb-developers] CrossDB class structure <br> <br> <DIV><FONT size=2>Hi Guys,</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Sorry I've been out of touch lately.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>As part of the generic db implementation I've been working on, I started creating a common base class and extending from that. Its mostly abstract classes that make it easier to create a db implementation. It's still very much a work in progress, but this is the general idea...</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>First a base class holds the info required for all queries, eg table name, and an abstract getQuery method.</FONT></DIV> <DIV><FONT size=2>This is then extended to implement the individual CrossDB interfaces such as CreateTable. This adds the rest of the methods required, addColumn, plus getter methods to return the stored details.</FONT></DIV> <DIV><FONT size=2>To implement a specific db the developer only need supply the getQuery method, using the getters, as all the rest of the interface is supplied by the abstract classes.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>I'll be spending a bit more time on the generic development now, and therefore the abstract classes, but it seems stupid for several of us to be doing the same thing. I can continue the generic stuff based on the CrossDB interfaces, but it would make more sense to get the basic class structure right first, otherwise we'll need to back-date any changes to the existing implemetations.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Kev.</FONT></DIV></BODY></HTML> |
|
From: KevinLentle <ke...@me...> - 2002-05-23 21:36:07
|
Hi Guys, Sorry I've been out of touch lately. As part of the generic db implementation I've been working on, I started = creating a common base class and extending from that. Its mostly = abstract classes that make it easier to create a db implementation. It's = still very much a work in progress, but this is the general idea... First a base class holds the info required for all queries, eg table = name, and an abstract getQuery method. This is then extended to implement the individual CrossDB interfaces = such as CreateTable. This adds the rest of the methods required, = addColumn, plus getter methods to return the stored details. To implement a specific db the developer only need supply the getQuery = method, using the getters, as all the rest of the interface is supplied = by the abstract classes. I'll be spending a bit more time on the generic development now, and = therefore the abstract classes, but it seems stupid for several of us to = be doing the same thing. I can continue the generic stuff based on the = CrossDB interfaces, but it would make more sense to get the basic class = structure right first, otherwise we'll need to back-date any changes to = the existing implemetations. Kev. |
|
From: James S. <jam...@ya...> - 2002-05-23 17:32:12
|
From: <tr...@th...>
> There's not too many matching methods here, for example CreateTableQuery.
>
> Only the execute methods match across teh board.
Though even just that would allow an abstract query dispatcher to process
queries polymorphically. Or use the composite pattern to produce a
BatchQuery and so forth.
> I guess we might have to work on seeing what can be made to match across
the baord. There are probably some inconsistencies.
I guess some statements take column names & values (Insert & Update), some
statements take where clauses (inserts, updates, deletes, selects but not
table manipulation or inserts). Whatever the database operation there's a
polymorphic execute() method.
Maybe there should be a WhereClause and ColumnValues objects to share common
semantics across these queries? It could well be that their implementations
could be shared across each database driver; afterall its mostly just the
SQL text that changes, or the fiddly JDBC special features that may get
used.
e.g. how about a class like this, like the existing WhereClause...
public class ColumnValues {
public void addColumn( String name, Object value ) {
...
}
public void addColun( String name, String value ) {
...
}
}
Then all the various addColumn/addWhereClause stuff is on those 2 objects.
Then we can make the Insert/Update/Delete interfaces much simpler
/** polymorphic API to any database operation */
public interface Operation {
public void execute(Connection connection) throws SQLException;
}
public interface InsertOperation extends Operation {
public void setColumnValues(ColumnValues values) {
...
}
}
public interface UpdateOperation extends Operation {
public void setColumnValues(ColumnValues values) {
...
}
public void setWhereClause(WhereClause where) {
...
}
}
public interface DeleteOperation extends Operation {
public void setWhereClause(WhereClause where) {
...
}
}
public interface SelectQuery extends Operation {
public void setWhereClause(WhereClause where) {
...
}
}
Then the interfaces become very simple; they are fairly polymorphic sort of,
and all the complex lots of methods (such as all the addColumn() methods or
addWhereCondition()). Then the differences between select, insert, update,
delete become more simple; which have a ColumnValues and which have a
WhereClause.
Incidentally for me the greatest value of crossdb is in a simple
adding/updating/deleting of data using a simple key/value approach rather
than the horrble SQL approach of using ? and passing in parameters. Having
this approach for where clauses would be cool too, though is a bit harder
for complex queries but would work a treat on views.
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|
|
From: <tr...@th...> - 2002-05-23 17:09:44
|
There's not too many matching methods here, for example CreateTableQuery. Only the execute methods match across teh board. I guess we might have to work on seeing what can be made to match across the baord. There are probably some inconsistencies. Travis |
|
From: <tr...@th...> - 2002-05-23 17:00:39
|
Packaged up all implementations into same package. Removed dependencies. Travis |
|
From: <tr...@th...> - 2002-05-23 15:59:48
|
I added you as a developer so you can get in there.
Agreed on most things. I will remove the pool, I generally added that to have a very simple and easy to use pool when that is all you want.
I like the query interface idea too, I'll try working on that now.
Travis
---- Original Message ----
From: James Strachan <jam...@ya...>
Sent: 2002-05-23
To: cro...@li...
Subject: [Crossdb-developers] couple of comments...
After building the new javadocs via
ant maven:javadocs
I need to check in a new project.xml for the above to work for others, along
with a working maven:site to generate a website containing unit test
results, code style check report etc.
I've been taking a closer look at the code, here's a few initial comments.
* it might be a good idea to add some polymorphism to the
InsertQuery/UpdateQuery interfaces, e.g. the addColumn() methods. Also all
of the Query interfaces might want to derive from a common base interface,
say Query, which has the execute() method along with the addWhere clause
stuff.
* it looks like we need to add a new addColumn(String name, Object value)
method to the Insert/UpdateQuery interfaces to allow polymorphic access.
* maybe consider descoping com.crossdb.pool as there's so many open source
JDBC pool implementations around, all of which are well documented & fully
debugged with unit test cases etc. Maybe crossdb should just pick one and
use it instead. e.g. there's poolman and a few at jakarta-commons such as
dbcp
http://cvs.apache.org/viewcvs/jakarta-commons/dbcp/
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Crossdb-developers mailing list
Cro...@li...
https://lists.sourceforge.net/lists/listinfo/crossdb-developers
|
|
From: James S. <jam...@ya...> - 2002-05-23 07:43:17
|
After building the new javadocs via
ant maven:javadocs
I need to check in a new project.xml for the above to work for others, along
with a working maven:site to generate a website containing unit test
results, code style check report etc.
I've been taking a closer look at the code, here's a few initial comments.
* it might be a good idea to add some polymorphism to the
InsertQuery/UpdateQuery interfaces, e.g. the addColumn() methods. Also all
of the Query interfaces might want to derive from a common base interface,
say Query, which has the execute() method along with the addWhere clause
stuff.
* it looks like we need to add a new addColumn(String name, Object value)
method to the Insert/UpdateQuery interfaces to allow polymorphic access.
* maybe consider descoping com.crossdb.pool as there's so many open source
JDBC pool implementations around, all of which are well documented & fully
debugged with unit test cases etc. Maybe crossdb should just pick one and
use it instead. e.g. there's poolman and a few at jakarta-commons such as
dbcp
http://cvs.apache.org/viewcvs/jakarta-commons/dbcp/
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|
|
From: <tr...@th...> - 2002-05-23 04:33:05
|
Fixed. please try again. I removed all dependencies on outside projects.
travis
---- Original Message ----
From: James Strachan <jam...@ya...>
Sent: 2002-05-22
To: tr...@th..., cro...@li...
Subject: Re: [Crossdb-developers] fixed compile errors
> The compile errors should be fixed.
did you do the commit? I still get this; mostly StringUtils is missing in
CVS.
BTW thanks for the prompt help!
James
javac.compile:
[javac] Compiling 53 source files to C:\cvs\crossdb\target\classes
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:1
2: cannot re
solve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:9
: cannot res
olve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:9
: cannot res
olve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:9: cann
ot resolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:5
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:5
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:6
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:6
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
06: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
06: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
22: cannot r
esolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringUtils.SQL
escape((String)val) + "'";
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
63: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
63: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
95: cannot r
esolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringU
tils.SQLescape((String)val) + "'";
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:7
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:7
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:8
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:8
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
04: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
04: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
14: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
14: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
42: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
42: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
59: cannot r
esolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringUtils.SQL
escape((String)val) + "'";
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:52: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:52: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:62: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:62: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerInsertQuery.
java:111: ca
nnot resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerInsertQuery.
java:111: ca
nnot resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerInsertQuery.
java:125: ca
nnot resolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringUtils.SQL
escape((String)val) + "'";
[javac]
^
[javac] Note:
C:\cvs\crossdb\src\java\com\spaceprogram\sql\mysql\MySQLResultSet.java uses
or ove
rrides a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 32 errors
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Crossdb-developers mailing list
Cro...@li...
https://lists.sourceforge.net/lists/listinfo/crossdb-developers
|
|
From: James S. <jam...@ya...> - 2002-05-22 23:27:17
|
> The compile errors should be fixed.
did you do the commit? I still get this; mostly StringUtils is missing in
CVS.
BTW thanks for the prompt help!
James
javac.compile:
[javac] Compiling 53 source files to C:\cvs\crossdb\target\classes
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:1
2: cannot re
solve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:9
: cannot res
olve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:9
: cannot res
olve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:9: cann
ot resolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] import com.spaceprogram.util.StringUtils;
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:5
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:5
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:6
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleDeleteQuery.java:6
5: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
06: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
06: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
22: cannot r
esolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringUtils.SQL
escape((String)val) + "'";
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
63: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
63: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleInsertQuery.java:1
95: cannot r
esolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringU
tils.SQLescape((String)val) + "'";
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:7
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:7
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:8
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleSelectQuery.java:8
8: cannot re
solve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
04: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
04: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
14: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
14: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
42: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
42: cannot r
esolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\oracle\OracleUpdateQuery.java:1
59: cannot r
esolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringUtils.SQL
escape((String)val) + "'";
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:52: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:52: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:62: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerDeleteQuery.
java:62: can
not resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerInsertQuery.
java:111: ca
nnot resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac] ^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerInsertQuery.
java:111: ca
nnot resolve symbol
[javac] symbol : class SQLDateFormat
[javac] location: package jdbc
[javac] com.spaceprogram.jdbc.SQLDateFormat sqldf = new
com.spaceprogram.jdbc.SQLDat
eFormat();
[javac]
^
[javac]
C:\cvs\crossdb\src\java\com\thinkvirtual\sql\sqlserver\SQLServerInsertQuery.
java:125: ca
nnot resolve symbol
[javac] symbol : class StringUtils
[javac] location: package util
[javac] in_val = "'" +
com.spaceprogram.util.StringUtils.SQL
escape((String)val) + "'";
[javac]
^
[javac] Note:
C:\cvs\crossdb\src\java\com\spaceprogram\sql\mysql\MySQLResultSet.java uses
or ove
rrides a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 32 errors
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|
|
From: James S. <jam...@ya...> - 2002-05-22 23:20:26
|
From: <tr...@th...> > Wow! Thanks a lot James, just imported the new structure into cvs in crossdb module. I will fix the compile errors asap. Cool thanks! > > I assume the crossdb/src/com/crossdb... shoudln't be there as it is in crossdb/src/java/com/crossdb as well? Yes. I moved all the source code from all over in src/... and dbs/... into a single crossdb/src/java directory. James. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
|
From: <tr...@th...> - 2002-05-22 23:11:09
|
The compile errors should be fixed. Travis |
|
From: <tr...@th...> - 2002-05-22 23:03:38
|
Wow! Thanks a lot James, just imported the new structure into cvs in crossdb module. I will fix the compile errors asap. I assume the crossdb/src/com/crossdb... shoudln't be there as it is in crossdb/src/java/com/crossdb as well? Travis ---- Original Message ---- From: James Strachan <jam...@ya...> Sent: 2002-05-22 To: cro...@li... Subject: [Crossdb-developers] Ant / Maven build system available; but various compile errors I'm musing about adding a crossdb tag library to Jelly http://jakarta.apache.org/commons/sandbox/jelly/ I tried taking the latest of CVS. I noticed there's no Ant build system and that the code layout is a little strange. I started off by creating an Ant / Maven style directory structure and creating a Maven build, which will automatically create your code, run unit test cases, javadoc and creates a nice development website too. It follows the more usual Ant / Maven build directory system of... crossdb/ build.xml project.xml (Maven project file) src/ java/ all source code here... test/ unit test cases here... I found a few compile errors in the core stuff in com.crossdb.* and various compile errors in the other 2 packages. I'd be nice if you could implement some kind of build system and directory structure like the above; then folks could use your stuff a bit easier. Here's the build system using the latest source code from CVS (with compile errors right now) here:- http://www.apache.org/~jstrachan/crossdb.zip James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Crossdb-developers mailing list Cro...@li... https://lists.sourceforge.net/lists/listinfo/crossdb-developers |
|
From: James S. <jam...@ya...> - 2002-05-22 22:39:08
|
I'm musing about adding a crossdb tag library to Jelly http://jakarta.apache.org/commons/sandbox/jelly/ I tried taking the latest of CVS. I noticed there's no Ant build system and that the code layout is a little strange. I started off by creating an Ant / Maven style directory structure and creating a Maven build, which will automatically create your code, run unit test cases, javadoc and creates a nice development website too. It follows the more usual Ant / Maven build directory system of... crossdb/ build.xml project.xml (Maven project file) src/ java/ all source code here... test/ unit test cases here... I found a few compile errors in the core stuff in com.crossdb.* and various compile errors in the other 2 packages. I'd be nice if you could implement some kind of build system and directory structure like the above; then folks could use your stuff a bit easier. Here's the build system using the latest source code from CVS (with compile errors right now) here:- http://www.apache.org/~jstrachan/crossdb.zip James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
|
From: <tr...@th...> - 2002-05-09 22:04:12
|
Started an HSQL implementation. It's in cvs. Travis |
|
From: <tr...@th...> - 2002-05-06 16:35:18
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 5.50.4522.1800" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff>No progress yet. Still on wishlist so you're welcome to get it going. <br> <br> Travis <br> <br> ---- Original Message ---- <br> From: Terence Ingram <<a href="mailto:te...@so...">te...@so...</a>> <br> Sent: 2002-05-05 <br> To: <a href="mailto:dev...@cr...">dev...@cr...</a> <br> Subject: Postgres Implmentation <br> <br> <DIV><FONT face=Arial size=2>Any progress on a Postgres implementation or is it still part of the wish-list?</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>Terence</FONT></DIV></BODY></HTML> |
|
From: <tr...@th...> - 2002-05-06 16:34:27
|
Changed the lists to the sourceforge lists now, so please use those lists now. Follow this link to get on it. http://sourceforge.net/mail/?group_id=26533 Travis ---- Original Message ---- From: Terence Ingram <te...@so...> Sent: 2002-05-05 To: dev...@cr... Subject: Testing Testing that this si the correct mail list address. Would nice to add an email list link on the "How to get involved" page :) Terence |
3 messages has been excluded from this view by a project administrator.
