I wrote:
> I'd like to ship a product that can use a database if the
> customer has one, but does not require that one be installed.

Jon writes:
> Kinda kills the point of your application eh? How can you write an
> application that depends on a database and then not expect people to use
> one.

From: Steven J. Owens
> Probably because he wrote an application that depends on a
> database but wants to provide the user with the option of using their
> current database.

That *is* the general idea.

At a big site they may already be using a massive DB2 or Oracle
installation, and would prefer that our product hook into their existing
database.

For a small or demo site better not to require or use an existing database.
For demonstration purposes we could even keep our data in text files :).


I wrote:
> Frameworks like Turbine/Dash seem to require a database (and
> SQL?) but I can't count on one existing on the customer's system.

Jon writes:
> Wrong. Turbine does NOT require a database. Take a look at
> org.apache.turbine.db.DBNone.
[snip]
> Sigh, just read the code more closely before you make
> comments like that.

An up front hint would be useful :).

I was very interested in Dash, but stopped when it seemed to *require* a
JDBC database interface.  Seemed no point in looking at the code.

>From http://www.working-dogs.com/dash/ :
----
Requirements
[snip]
It also requires the latest version of the Element Construction Set and the
Village packages.
----

>From http://www.working-dogs.com/village/ :
----
[snip]
Village is a 100% Pure Java API that sits on top of the JDBC API.
----

Sure looks like I *must* have a database... :).  Glad to hear otherwise.

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to