--
+--------------------------------+---------------------------------------+
| Gerald W. Lester |
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+
It also depends on why you want to avoid RDBMSs in the first place.
If you'd like a database, but don't want all of the negatives that
typically come along for the ride (overhead, maintenance, setup,
backups, etc), you might be interested in SQLite or Metakit. Both
just work - no installation, no setup, no server, no hassle, no sweat!
I'm working on just such a project now - using Tcl and SQLite...
Jeff
It depends on the kind of application you are trying to build. Most
game applications probably don't need a full on relational database,
for instance.
However, most applications need some sort of database. With what are
you actually struggling? The cost of rdbms? Not knowing how to program
a web app to use one?
Be more specific about the concerns you have and perhaps you can get
more information that is relevant to your concerns.
I have several large, very-long-term projects that rely
on the ZODB OODBMS that Zope builds in. I wonder how
gavino, the original poster, regards OODBMS in relation
to his question.
The first functional public commerce server stored its records in the
file system too, as Tcl data.
So, yeah, it is.
--
Darren New / San Diego, CA, USA (PST)
I bet exercise equipment would be a lot more
expensive if we had evolved from starfish.
Also, don't forget that some webapps have nothing to do with
databases. Examples include such things as HTML validators and
calculators of various sorts.
Or just plain web sites:
Is coded completely in Tcl (using Don Libes's cgi.tcl package). And
makes no use of a database.
>
>
>
>
--
Robert Heller -- Get the Deepwoods Software FireFox Toolbar!
Deepwoods Software -- Linux Installation and Administration
http://www.deepsoft.com/ -- Web Hosting, with CGI and Database
hel...@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk
I don't think anybody is against your asking. Probably nobody quite
understood your question. So, is what you really want to know whether
the kinds of webapps that require a database back end must necessarily
use a relational database rather than an object-oriented database?