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

Dave Segleau dave.segleau at oracle.com
Wed Feb 17 11:06:56 PST 2010


Luis,

Thanks for the reply. I wanted to follow up on Sandra's email from this 
morning. We're looking into your questions in more depth, but I just 
want to make sure we understand what it is that you're trying to do so 
that we're answering the right questions. We understand that you have 
existing applications, built with various Oracle development tools. Some 
of these applications use the Oracle Database Server and some apparently 
use Berkeley DB Java Edition.

    * Specifically, which application development tool are you trying to
      use to build /this /application?
    * Is this a new application, specifically for the mobile platform?
      Or is it a single application with two modes: a) connected to an
      Oracle Server database and b) disconnected, running on a
      smartphone device with SQLite/Berkeley DB installed locally?
    * Does this new application plan to use Berkeley DB 11gR2 via the
      SQL API, which is based on SQLite?
    * Does this new application plan to access the SQLite/Berkeley DB
      database via JDBC?
    * Does this new application plan on using capabilities of the SQLite
      spatial functionality, just simple SQL or something else?

With regards to your recent question:

    "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?"

Berkeley DB Java Edition is not the same library as the Berkeley DB 
11gR2 Beta release. They are two separate products. Berkeley DB Java 
Edition does not have support for a SQL API -- it provides a Key/Value 
pair API, a Java collections API and a Data Persistence Layer API for 
POJO-style Java Object persistence. The Berkeley DB 11gR2 Beta release 
library is written in C, has the same API support and is the product 
that is introducing a new SQL API, based on integration of the SQLite 
library. How you build, link and deploy Berkeley DB Java Edition vs 
Berkeley DB is different.

In the case of Berkeley DB Java Edition, being referenced in a 
JDeveloper Application, all you needed was the Berkeley DB Java Edition 
jar file.

In the case of Berkeley DB 11gR2 Beta, the SQL API is based on SQLite. 
As such, your build, link and deployment process would be different than 
using Berkeley DB Java Edition. Essentially, you would want to do the 
following:
a) build the Berkeley DB 11gR2 library from source;
b) download the SQLite JDBC driver package from 
http://www.ch-werner.de/javasqlite/;
c) using the package and the instructions from step b), build a 
sqlite.jar and libsqlite_jni.dll based on the libsqlite3.dll that was 
built/generated from step a),
d) you should then be able to build and run a Java application that 
calls the SQLite Java interface using the JDBC driver from step c),

Does this make sense and does it help you make forward progress?

If we're still not in sync with regards to what you're trying to do, we 
can either continue to have this discussion via email or get on a 
conference call. Please let me know if you would like to schedule a call 
and what time works best for you. I just want to make sure that we 
properly understand what it is that you are trying to build.

Regards,

Dave

On 2/17/2010 4:20 AM, Luis Paolini wrote:
> 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
>    
-- 
Oracle <http://www.oracle.com>
David Segleau | Director Product Management - Berkeley DB
Phone: +1 425 945 8533 | Mobile: +1 408 420 7350
Oracle Database Engineering

Green Oracle <http://www.oracle.com/commitment> Oracle is committed to 
developing practices and products that help protect the environment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/bdb-beta-feedback/attachments/20100217/1793928e/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oracle_sig_logo.gif
Type: image/gif
Size: 658 bytes
Desc: not available
Url : http://oss.oracle.com/pipermail/bdb-beta-feedback/attachments/20100217/1793928e/attachment-0002.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: green-for-email-sig_0.gif
Type: image/gif
Size: 356 bytes
Desc: not available
Url : http://oss.oracle.com/pipermail/bdb-beta-feedback/attachments/20100217/1793928e/attachment-0003.gif 


More information about the BDB-BETA-FEEDBACK mailing list