|Subject||Re: [Firebird-Java] Re: Anyone have a CLEAR example of . . .|
I haven't had the problems with simple stuff that this guy has, but trying to do anything else has a steep learning curve because you have to analyze source code. A simple javadoc would help a lot. I'd offer to do it myself but I don't understand the driver well enough to do a competent job.
Thanks for all your efforts!
----- Original Message -----From: David JencksSent: Wednesday, July 03, 2002 8:04 AMSubject: Re: [Firebird-Java] Re: Anyone have a CLEAR example of . . .Did you try running the tests?
get the source from cvs
If they don't pass, you know something is very wrong with your environment.
I was under the impression that using MSSQL commercially was rather
expensive. I suspect that if you offerred to pay someone the money you
would otherwise be paying MS to write better instructions and examples and
improve the usablity of the firebird driver you would get takers and quick
On 2002.07.03 01:21:10 -0400 jarrodhroberson wrote:
> --- In Firebird-Java@y..., "rrokytskyy" <rrokytskyy@y...> wrote:
> > > in the top-secret open source tree in cvs.
> > I must admit, you're in a good mood! :)
> > BTW, what about moving tests from src/ to test/ directory?
> > Have a nice weekend!
> > Roman
> yeah, that might be a little more intutative.
> Also, it thoses tests do not solve the simple problem of having a
> simple clear example, they are way obfuscated with lots of static crap
> in superclasses and other overly complex indirection, and have all
> those dependancies on the JUnit and Log4J, they are _NOT_ _CLEAR_
> I am NOT a newbie and I spent plenty of time trying to find the
> examples and information, get them, DECIPEHER them, and to get it to
> work. As of a couple hours wasted later, no worky. Interclient works
> first time out of the box with some clear examples.
> I should not be this hard to simple load the driver, get a connection
> to a local database and execute a sql statement. All the sql I
> executed returned the same _USELESS_ error, one of those "oh shit
> something happened" errors that does not tell any useful information.
> The SQL Statement was "SELECT PERSON_ID FROM PERSON". Does not get
> simpler than that.
> Probably just switch the project over to MS SQL Server, they have a
> more robust and full feature Type 4 driver ( that is a beta also )
> that works first time out of the box no problems.
> Good luck guys on the development of this Driver it has a ways to go
> for prime time.