[BDB 11gR2 Beta] [#18298] First Questions about DBD 11gR2

[Luis Paolini]

Hi Sandra,

	Thank you for the answers.
	I have an additional question based on the answer for question 2.

	Additional Question 2:
	I used to work with BDB as a single jar file (like je-3.3.87.jar)
that was referenced in a JDeveloper Application.
	For deployment, this jar file was packed with my application
libraries and files to be deploy to the client.
	Now it seems that this process must be changed. The way to install
BDB in a windows machine will consider some
	Dlls installation. Is this correct?

Regards,

Luis Paolini


-----Original Message-----
From: Sandra Whitman [mailto:sandra.whitman at oracle.com] 
Sent: domingo, 14 de fevereiro de 2010 22:48
To: Luis Paolini
Cc: bdb-beta-feedback at oss.oracle.com; support at sleepycat.com; Whitman,Sandra
Subject: Re: [BDB 11gR2 Beta] [#18298] First Questions about DBD 11gR2

Hi Luis,


Thank you again for your email.  I have been investigating your 
questions and do have some answers which I will list below in the 
question/answer section.  I am still doing some more research regarding 
ADF and JDBC access and will get back to you on those. In the mean time 
if you have any other questions, or if I did not completely answer 
something, please let me know.


Question 1:
Is necessary to build BDB from source files?

Answer 1:
At the current time you do need to build Berkeley DB from source.  This 
requires Visual Studio C++.  You can use the free Express version 
available from Microsoft.com.  We will however consider a pre-built 
version for the future.

Question 2:
How is the BDB jar file obtained?

Answer 2:
What are the plans for the Berkeley DB jar file?  Is that to be used 
with ADF?  I am still checking, but a jar file may not be
needed for this.  If a Berkeley DB jar file is needed, it can be built 
with Version 1.5 or 1.6 of the Java JDK.


Question 3:
How is BDB configured to support SQL?

Answer 3:
SQL support is built automatically on Windows. The SQL library is built 
as libdb_sql50.dll in the Release mode or libdb_sql50d.dll in the Debug 
mode. An SQL command line interpreter called db_sql_shell.exe is also 
built.

Please take a look in the documentation titled "Building the SQL API - 
Chapter 5. Building Berkeley DB for Windows"

 From there:
Building the SQL API

Binary Compatibility With SQLite

SQL support is built automatically on Windows. The SQL library is built 
as libdb_sql50.dll in the Release mode or libdb_sql50d.dll in the Debug 
mode. An SQL command line interpreter called db_sql_shell.exe is also built.
Binary Compatibility With SQLite

Both libdb_sql50.dll and libdb_sql50d.dll are compatible with 
sqlite3.dll. You can rename libdb_sql50.dll to sqlite3.dll and 
db_sql_shell.exe to sqlite3.exe, and use these applications as a 
replacement for the standard SQLite binaries with same names.


Question 4:
Are the SQLite data types are supported by Oracle ADF?

Answer 4:
I am still investigating this point.  However, the ADF  components 
support SQLite so there should not be a problem here.
I will get back to you on this though.


Question 5:
Is any documentation available regarding JDBC access to the database.

Answer 5:
The ODBC and JDBC drivers are not included in the initial Beta release 
package, but they are supported and they will be included in the 
production release. In order to build the drivers, please download the 
open source ODBC driver from http://www.ch-werner.de/sqliteodbc/ and the 
open source JDBC driver from http://www.ch-werner.de/javasqlite.


Question 6:
Are there any examples using BDB SQLite Interfaces?

Answer:
The BDB SQLite interface examples are under the distribution at 
sql\examples\c.


Best Regards,
Sandra
Sandra Whitman
Oracle Global Customer Support




__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4866 (20100214) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4873 (20100217) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com