Board index » cppbuilder » ANN: dbGonazles database for Delphi, Kylix and C++Builder

2004-01-27 06:00:27 PM
cppbuilder57
Hello Developers,
we are glad to inform you, that the dbGonzales Database for Delphi has
reached its public beta state.
dbGonzales is a high speed object oriented client/server database. Here
are some of its unique features:
- the object oriented database design enables you, to develop your
applications faster.
- migrate your relational databases to higher performance.
- a SQL query engine will be available in the final version.
- scalable to your needs: from embeded single user to multi-user and
client/server.
- eliminate performance bottlenecks with our highly optimized database
engine.
- the client based query engine guarantees better performance and less
load on the server and the net.
- secure and crash proof filesystem for your valuable data.
- use transactions for your data consistency.
- object oriented design allows you to expand our database-engine to
your needs.
- 100% written in Delphi.
- TDataSet component available.
- easy development - easy installation - easy administration.
We have published some benchmarks on our web-site www.db-gonzales.de
You can also download two demo-applications.
One is an dbGonzales implementation of a benchmark released on the
SQLite web-site. In this benchmark program, dbGonzales beets SQLite on
all operations, most of the time between factor 2 to 10. (SQLite claims
to be twice as fast as MySQL!!)
This demo is a single file and includes the embedded dbGonzales
single-user engine.
Codesize 553 KBytes
The other is a graphical demo, which shows database updates in real-time
and thus creating an animation. This demo also makes use of the
oo-features build in dbGonzales (Virtual method invocation of the
objects stored in the database - used for painting).
This demo is a single file and includes an embedded dbGonzales server
and the client TDataSet componentes.
Codesize 827 KBytes
We will give time limited evaluation components to interested developers.
In the beta test period, we support only Delphi 5, Delphi 7 and Kylix 3.
Please contact me per email: XXXX@XXXXX.COM
Best regards,
Adrian Veith.
--
Veith System GmbH.
Tel: +49-(0)8052-2636
Fax: +49-(0)8052-4019
 

Adrian,
attractive is the fact that the client has to poll the server
all the time in order to remain updated.
e.g., your GDemo is nice, but it clocks to about 70 % CPU load on
a dual-opteron Win2K machine here.
I'd like to have my servers to be big and powerful but the clients
to be thin and cheap. Which means I'd rather not have to poll the
server from the client every x miliseconds.
What I have been longing to see is an OO database with some sort
of publish-subscribe (event-driven) mechanism whereby the client
tell the server which classes or objects it is interested in and
the server notifies the client only when any one of those classes
or objects changed.
Something along this metaphor would be great.
Any chance of that happening?
Cheers,
Adem
 

Hi Adem,
Adem schrieb:
my machine stays at 1% Load. If something has to be updated, then it is
this something that causes the load (on my machine, the drawing of the
objects takes about 80% of time - the refresh rate is much higher if you
comment out the call to Canvase.Ellipse etc.).
transaction to get updated. Otherwise you can poll in a "reasonable"
time frame. Only the animation character of the GDemo makes it necessary
to poll every 40ms to get the feeling of an animation.
components and the server components) ->it is quite easy to expand the
server to your needs.
You can write an event-handler on the server-application, which informs
registered clients if something has changed. Currently we don't see the
need to implement something like this on our own, but it is not a big
thing. If anybody is interested in doing this, we help him.
Adrian.
 

{smallsort}

Adrian,
reusable fashion needs more than casual coding. I mean, what I would
like to see is a database that works with its clients much more closely
so that the client gets to know that
i) an object it currently refers to has been deleted/updated etc.
ii) a new object has been added to the dataset the client has cahced
(i.e. falls within the boundaries of the query that created the dataset)
iii) Some other client has tried to issue a lock request that this
client has a lock on. So that I can warn the user to get on with it.
There are many more such things and it seems i'll have to wait another
generation for even a subset.
BTW, can't you use something like what InstantObjects is doing. It
is MPL open source as you probably know.
Cheers,
Adem