on 5/31/02 20:50, Ken & Deb Allen at kendrhyd /at/ sympatico DOT ca wrote:
> I understand about the JOIN syntax, and the foreign keys and indexes. I
> know that there are other ways of doing things, and Valentina seems to
> promote a mechanism that embeds the data and database access in classes,
> which reflects its strong OO background. The ability to parse Data
> Definition Language forms of SQL (such as defining indexes and foreign
> keys) and have these automatically (and transparently) result in the
> proper Valentina constructs would be incredibly compelling (from a
> technical point of view).
>
> I get the impression from the documentation and your comments that
> Valentina is primarily a memory based database, with the contents being
> stored on the disk when the database is shutdown or 'checkpointed'. Is
> this actually the case?
NO !!!
Valentina is NOT RAM-based DBMS.
Valentina perfectly work with huge database, when size of db files >> of RAM
size. In fact Valentina is MORE optimized for such big dbs. For smaller dbs
I still have a lots of way to improve. In fact Valentina even do not have
yet such feature as RAM based tables. Each TMP table go to disk, and this is
where I have potential speed up Valentina for small results of queries,
--
Best regards,
Ruslan Zasukhin
-------------------------
Paradigma.
e-mail: ruslan@paradigmasoft.com
web : http://www.paradigmasoft.com
To subscribe to the Valentina mail list
send a letter to valentina-on /at/ lists DOT macserve.net
©2002 Ruslan Zasukhin |
