I'm currently "mavenising" jOOQ. This means that trunk may not really
compile for a while, sorry about that.
Cheers
Lukas
> I can live with that for a while :-)
That's great, because you don't have a choice :-)
> By the way, I have come a long way with the Sybase support. At the moment
> there are about 7 tests that are failing.
Great news! Feel free to make partial commits if you think that other
RDBMS's functionality won't be affected. I'm a bit worried that maybe
with next week's refactorings due to "mavenising" jOOQ, you might have
quite a diff in your workspace... If Sybase isn't ready by the next
release, I can simply exclude that from the release-build...
Otherwise, we can release it as "beta"
Also note, that some integration tests are currently failing because
of a refactoring due to these tickets:
https://sourceforge.net/apps/trac/jooq/ticket/391
https://sourceforge.net/apps/trac/jooq/ticket/392
https://sourceforge.net/apps/trac/jooq/ticket/396
Cheers
Lukas
I have one more question:
Since you'll be committing Sybase code soon, I will have to install a
test database on my computer, I guess. For Oracle, I installed Oracle
XE, which is quite slim and stripped down to the essentials. Is there
anything similar for Sybase? Can you point me to the best-suited
Sybase product? Is it SQL Anywhere?
http://www.sybase.com/products/databasemanagement/sqlanywhere
Cheers
Lukas
2011/4/10 Lukas Eder <lukas...@gmail.com>:
As you wish... On the other hand, I don't think that a complete Maven
release will be possible with version 1.5.7.
In the mean time, these have been the decisions:
- jOOQ-test will not be "mavenised". It depends too much on a working
Eclipse workspace and running database connections
- jOOQ-codegen and jOOQ should be more or less ready as they are
So there aren't many big project restructurings coming up...
> I've checked out the latest version and I have manually modified the pom's
> and classpath so that the projects compile.
Good to know. Did everything work out well? Also with the dependency
on ojdbc6, which you have to establish manually at your site?
Cheers
Lukas
OK, perfect. I'll try installing it sometime this week
> I have checked out the lastest revison and with some manual adjustments of
> the pom's the projects still compiles. I continue my task of implementing
> Sybase support.
You really don't want to check in, do you? :-)
I will continue to add rocks in your path. You'll see. I'm quite
heavily refactoring jooq-codegen. Happy merge, I'd say! :-)
I know we talked about you being electrocuted and beheaded before
where you used to work. But I can live with 1-2 incomplete checkins.
Really... Well it's up to you :-)
Cheers
Lukas
Awesome!
> My plan is to commit my work so far in a couple of days. This will be an
> incomplete commit though, there are still some unit tests that fail.
I can help you as soon as you have committed. By the next release, I
also plan to integrate SQL Server on popular request. Then we'll have
support for almost all major RDBMS. I guess Ingres and Firebird might
be useful on the roadmap with a low prio...
Cheers
Lukas
Thanks! That's quite a commit. I'm about to review it. :-)
Unbelievable how those dialects are just slightly different, right?
"current date" instead of "current_date"... whatever ;-)
I have downloaded SQL Anywhere 12 and it runs fine on my computer. But
how can I connect with JDBC? Is there anything specific I need to set
up? I get this kind of exception:
java.sql.SQLException: JZ006: IOException: java.net.ConnectException:
Connection refused: connect wurde abgefangen
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseErrorCheckDead(Unknown Source)
Googling will probably lead me to the solution eventually, but maybe
you have an idea?
Cheers
Lukas