Subject | Re: simple script to connect Firebird |
---|---|
Author | rrokytskyy |
Post date | 2002-07-19T13:37:27Z |
Richard,
jdbc:oracle:thin:user/passwd@...:1521:ora_db
:)
project it was already so, so nobody changed it later. Maybe it was
easier to parse the string into components... If you wish, you can
check org.firebirdsql.jgds.GDS_Impl.DBAttachInfo and create a patch
that will support both schemes. If nobody has anything against it, we
will commit it to the CVS. Personally I do not have anything against
it but I would not invest time into this as well.
Alejandro? David? Blas? Any comments on this?
Best regards,
Roman Rokytskyy
> You know, I had problems initially with this as well until I sawWell... One can argue about URLs, Oracle for example has
> the DriverExample - then it all worked fine. The big difference
> was the database URL. Formerly, Interclient (and every other JDBC
> driver I'd used including PostgreSQL) had a connection string that
> looked like this:
>
> jdbc:interbase://myHost/opt/interbase/examples/employee.gdb
>
> now it looks like this:
>
> jdbc:firebirdsql:myHost/3050:/opt/interbase/examples/employee.gdb
jdbc:oracle:thin:user/passwd@...:1521:ora_db
:)
> I'm not totally familiar with the JDBC specifications, so I don'tAs far a I know, URL format is not specified. When I joined the
> know if the URL was changed to be in accordance with JDBC 2.0 or
> something else. I'm just curious - why did it change?
project it was already so, so nobody changed it later. Maybe it was
easier to parse the string into components... If you wish, you can
check org.firebirdsql.jgds.GDS_Impl.DBAttachInfo and create a patch
that will support both schemes. If nobody has anything against it, we
will commit it to the CVS. Personally I do not have anything against
it but I would not invest time into this as well.
Alejandro? David? Blas? Any comments on this?
Best regards,
Roman Rokytskyy