Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of st.never@gmail.com designates
 74.125.82.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <10126092-2563-4D60-A82B-ECEA24B2A287@sbcglobal.net>
References: <10126092-2563-4D60-A82B-ECEA24B2A287@sbcglobal.net>
Date: Mon, 5 Mar 2012 09:34:09 -0300
Message-ID: 
 <CAAixLiSBL_zn7mhaDPrUHNqm+pr1oyAwvAqJH-OobtNYz_+osQ@mail.gmail.com>
Subject: Re: How to approach Derby embedded?
From: =?ISO-8859-1?Q?Jos=E9_Ventura?= <st.never@gmail.com>
To: Derby Discussion <derby-user@db.apache.org>
Content-Type: multipart/alternative; boundary=f46d043891bfa024a204ba7e2400

--f46d043891bfa024a204ba7e2400
Content-Type: text/plain; charset=ISO-8859-1

The first question would be, "Is JDBC too much for me?"

If you are familiar with JDBC and frameworks built upon it (Hibernate,
etc), then Derby's required configuration is definitely tiny by comparison.
You can run an embedded database by just:

   - adding derby.jar to your classpath (if using maven, that's already
   done for you)
   - specifying your JDBC url as
   "jdbc:derby:path/to/database/directory;create=true"
   - specifying your JDBC driver as "org.apache.derby.jdbc.EmbeddedDriver"

Once you get a JDBC Connection you can use it to execute CREATE TABLEs and
the like, and then you're ready to go.

If you aren't familiar with JDBC (or think it is overkill as well), then
maybe you could take a look at other persistent stores: the only one that
comes to my mind right now is Prevayler <http://prevayler.org/>, but I'm
sure there are several others (I know of several NoSQL stores -- but if
Derby is overkill for you then I suppose they will be too).

Just my 2 cents.

On Sat, Mar 3, 2012 at 7:51 PM, Kenneth McDonald <
kenneth.m.mcdonald@sbcglobal.net> wrote:

> I need a very simple (even SQL is more than what I need) embedded database
> for some persistent stores. Derby seems like it would be ideal, except that
> even configuring seems to require more than what I need. In particular, I'm
> seeing in the docs that I need to edit my class path (which I shouldn't
> need to do for my purposes), that I may need to set up more complex
> configurations (than I need for my purposes), etc. etc. Can this be
> simplified?
>
> More specifically; I have Derby downloaded and installed via Maven
> (actually via SBT in Scala). I want to run it as a purely embedded jar, to
> provide persistent store and dirt-simple queries. I don't want to worry
> about shell variables, CLIs, or any similar hooey--just the simplest
> possible SQL to store/access my data. Can I do this with Derby?
>
> My comparison point is bdb the way bdb was under Python several versions
> ago--not the way bdb has become more recently. Can I achieve a similar
> level of simplicity?
>
> Thanks,
> Ken

--f46d043891bfa024a204ba7e2400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The first question would be, &quot;Is JDBC too much for me?&quot;<div><br><=
/div><div>If you are familiar with JDBC and frameworks built upon it (Hiber=
nate, etc), then Derby&#39;s required configuration is definitely tiny by c=
omparison. You can run an embedded database by just:</div>
<div><ul><li>adding derby.jar to your classpath (if using maven, that&#39;s=
 already done for you)</li><li>specifying your JDBC url as &quot;jdbc:derby=
:path/to/database/directory;create=3Dtrue&quot;</li><li>specifying your JDB=
C driver as &quot;org.apache.derby.jdbc.EmbeddedDriver&quot;</li>
</ul><div>Once you get a JDBC Connection you can use it to execute CREATE T=
ABLEs and the like, and then you&#39;re ready to go.</div></div><div><br></=
div><div>If you aren&#39;t familiar with JDBC (or think it is overkill as w=
ell), then maybe you could take a look at other persistent stores: the only=
 one that comes to my mind right now is <a href=3D"http://prevayler.org/">P=
revayler</a>, but I&#39;m sure there are several others (I know of several =
NoSQL stores -- but if Derby is overkill for you then I suppose they will b=
e too).</div>
<div><br></div><div>Just my 2 cents.</div><div><br><div class=3D"gmail_quot=
e">On Sat, Mar 3, 2012 at 7:51 PM, Kenneth McDonald <span dir=3D"ltr">&lt;<=
a href=3D"mailto:kenneth.m.mcdonald@sbcglobal.net">kenneth.m.mcdonald@sbcgl=
obal.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I need a very simple (even SQL is more than =
what I need) embedded database for some persistent stores. Derby seems like=
 it would be ideal, except that even configuring seems to require more than=
 what I need. In particular, I&#39;m seeing in the docs that I need to edit=
 my class path (which I shouldn&#39;t need to do for my purposes), that I m=
ay need to set up more complex configurations (than I need for my purposes)=
, etc. etc. Can this be simplified?<br>

<br>
More specifically; I have Derby downloaded and installed via Maven (actuall=
y via SBT in Scala). I want to run it as a purely embedded jar, to provide =
persistent store and dirt-simple queries. I don&#39;t want to worry about s=
hell variables, CLIs, or any similar hooey--just the simplest possible SQL =
to store/access my data. Can I do this with Derby?<br>

<br>
My comparison point is bdb the way bdb was under Python several versions ag=
o--not the way bdb has become more recently. Can I achieve a similar level =
of simplicity?<br>
<br>
Thanks,<br>
Ken</blockquote></div><br></div>

--f46d043891bfa024a204ba7e2400--