I'm getting really confused on the TEDBEngine.ConfigMemory and it's use.

<<
Tim said:

You might want to look into using the TEDBEngine.ConfigMemory property
that is new in 2.04.  This is really the property that you want, since
it will allow you to keep the configuration in memory in the
application, and use the CREATE/ALTER DATABASE statement to keep
changing the location of the database that you're accessing without
constantly updating an on-disk configuration file.

The manual says:

Use this statement to create a new database. If the path specified for
the database is not valid, then ElevateDB will attempt to create the
path. Specifying the IN MEMORY keywords instead of a path will result
in the database being created in memory.

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=CREA
TE_DATABASE

>>

If I set the TEDBEngine.ConfigMemory:= True does the database and
tables still reside on-disk? Where can I find an example of how to do
this?

--
Michael Riley
GySgt USMC Retired
www.zilchworks.com

Michael,

<< If I set the TEDBEngine.ConfigMemory:= True does the database an tables
still reside on-disk? >>

Yes.  The only thing that doesn't reside on disk anymore is the
configuration file (EDBConfig.EDBCfg file).  This file contains the
database, store, user, role, and job definitions, so if you use the
ConfigMemory=True setting, you'll need to create those on-the-fly at
application startup because they won't exist each time the application is
started.

The statements that you'll need to do this are:

CREATE DATABASE
CREATE STORE
CREATE USER
CREATE ROLE
CREATE JOB

although I suspect the only ones you'll need is the CREATE DATABASE
statement, and possibly the CREATE USER and CREATE ROLE statements.  When
using the in-memory configuration the user security is in its default state
at application startup, meaning that the default Administrator account will
be present along with the default Administrators and Public roles.

--
Tim Young
Elevate Software
www.elevatesoft.com