| Connection Profile vs. Driver Definitions [message #21022] |
Wed, 23 August 2006 21:25  |
Eclipse User |
|
|
|
What is the difference between a connection profile and a driver
defintion. I can create a connection to a derby database using either
the Derby Embedded Database or the SQL Model-JDBC Connection. What is
the difference? Why would I choose one over the other? Would I get
different functionality? Do they use different models?
Is Derby Embedded Database really specific to embedded databases or does
it apply to networked Derby databases as well?
|
|
|
|
| Re: Connection Profile vs. Driver Definitions [message #21260 is a reply to message #21022] |
Thu, 07 September 2006 14:07  |
| Eclipse User |
|
|
|
> What is the difference between a connection profile and a driver
> defintion. I can create a connection to a derby database using either
The driver definition is used for specifying details for a particular
server type; e.g. driver class name, driver jars, etc. In addition to
these, the driver definition may specify default values for things like
connection URL, user id, vendor & version, etc.
A connection profile specifies the details for connecting to a particular
server (e.g. connection URL, uid, pwd, etc.) A connection profile may
reference a driver definition (for most of the db types in DTP, this is
true).
> Is Derby Embedded Database really specific to embedded databases or does
> it apply to networked Derby databases as well?
The Derby embedded database is specific to the embedded database. The
reason for this is that Derby embedded does not support multiple
connections (a singleton instance is shared by all at the connection
factory level; i.e. subsequent IConnectionFactory.createConnection()
requests return the same connection, in addition to bumping up the
reference count) and it does not support java.sql.Connection.close() (to
close you must use java.sql.Driver.connect() with a close URL).
For networked Derby, you should use the generic JDBC profile (SQL
Model-JDBC Connection).
Hope that helps.
Rob
|
|
|
| Re: Connection Profile vs. Driver Definitions [message #581923 is a reply to message #21022] |
Sat, 26 August 2006 18:28 |
| Eclipse User |
|
|
|
The Driver Definitions are typically provided by the database vendor and
wud include the database specific JDBC library. The connection created
using SQL Model-JDBC Connection will have only basic features that are
common to all databases and nothing specific to a particular database.
For Eg. mechanism to debugg a procedure is different from one database
to another and so I would not expect this feature to be available in SQL
Model-JDBC Connection and may be available from the vendor
provided/specific profile.
Anthos
Christopher M. Judd wrote:
> What is the difference between a connection profile and a driver
> defintion. I can create a connection to a derby database using either
> the Derby Embedded Database or the SQL Model-JDBC Connection. What is
> the difference? Why would I choose one over the other? Would I get
> different functionality? Do they use different models?
>
> Is Derby Embedded Database really specific to embedded databases or does
> it apply to networked Derby databases as well?
|
|
|
| Re: Connection Profile vs. Driver Definitions [message #582191 is a reply to message #21022] |
Thu, 07 September 2006 14:07 |
| Eclipse User |
|
|
|
> What is the difference between a connection profile and a driver
> defintion. I can create a connection to a derby database using either
The driver definition is used for specifying details for a particular
server type; e.g. driver class name, driver jars, etc. In addition to
these, the driver definition may specify default values for things like
connection URL, user id, vendor & version, etc.
A connection profile specifies the details for connecting to a particular
server (e.g. connection URL, uid, pwd, etc.) A connection profile may
reference a driver definition (for most of the db types in DTP, this is
true).
> Is Derby Embedded Database really specific to embedded databases or does
> it apply to networked Derby databases as well?
The Derby embedded database is specific to the embedded database. The
reason for this is that Derby embedded does not support multiple
connections (a singleton instance is shared by all at the connection
factory level; i.e. subsequent IConnectionFactory.createConnection()
requests return the same connection, in addition to bumping up the
reference count) and it does not support java.sql.Connection.close() (to
close you must use java.sql.Driver.connect() with a close URL).
For networked Derby, you should use the generic JDBC profile (SQL
Model-JDBC Connection).
Hope that helps.
Rob
|
|
|
Powered by
FUDForum. Page generated in 0.04165 seconds
Home