There's a new ElevateDB preview available now.  There are some format
changes to the configuration files and catalogs, so you'll need to re-create
or re-migrate any databases again in order to use the new preview.  Don't
try to use existing databases or configuration files from the last preview
with this new preview or you'll run into problems.

The new preview has these changes specifically:

- Databases are not tied to a specific configuration file any more, and are
generically named so that any existing database can be used with an existing
configuration file by simply using a CREATE DATABASE statement to
re-establish a link by adding a new database to the configuration file.

- The RowID column is gone.  Tables with no primary key defined will be
accessed in a "natural order" that corresponds to the order in which the
rows were added.

- A bunch of miscellaneous bugs were fixed.

There will most likely only be one or two more preview builds before the
final release on January 31, 2007.

More than likely there will be a couple of fairly quick minor version
releases in February and March as new features are added to EDB to fullfill
existing enhancement requests and as new enhancement requests come in.

Unicode support is present in EDB, but we still have some items to address
in the build system before we can do separate Unicode and ANSI previews.  I
will keep everyone posted as to when a Unicode preview will be available.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hello Tim,

> Unicode support is present in EDB, but we still have some items to address
> in the build system before we can do separate Unicode and ANSI previews.  I
> will keep everyone posted as to when a Unicode preview will be available.

My mail server is waiting for this!

--
Charalabos Michael - [Creation Power] - http://www.creationpower.com -
http://www.creationpower.gr

Tim

>- The RowID column is gone. Tables with no primary key defined will be
>accessed in a "natural order" that corresponds to the order in which the
>rows were added.

Make sure you give this prominence in the "what's new" bit of the manual please. I have several tables using the RowID catenated with other fields to give me the ordering I want (eg sequence entered within date).

I'm assuming that the upgrade/conversion from DBISAM to ElevateDB will simply dump RowID. Is that the case? If not what will happen to it (possibly converted to an autoinc column)?

Roy Lambert

Roy,

<< Make sure you give this prominence in the "what's new" bit of the manual
please. I have several tables using the RowID catenated with other fields to
give me the ordering I want (eg sequence entered within date). >>

I assume you mean "RecordID", and yes, I will.

<< I'm assuming that the upgrade/conversion from DBISAM to ElevateDB will
simply dump RowID. Is that the case? If not what will happen to it (possibly
converted to an autoinc column)? >>

Right now the migration moves the RecordID column over "as-is" and keeps it
as a plain integer.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy,

Forget what I just said (got a million things going on .   RecordID is
dumped in the migrate process because it is not visible, and any indexes
that reference RecordID are dumped also because there's no way of knowing
how to construct the index is RecordID isn't present.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


I know its more work for you but is there a chance of making it optional to transfer as an autoinc (which I think best preserves what it is now)?

Roy Lambert

Roy,

<< I know its more work for you but is there a chance of making it optional
to transfer as an autoinc (which I think best preserves what it is now)? >>

For every table ?  How is EDB to know whether to transfer it or not ?  I
guess we could do it only if it is referenced in an index.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>For every table ? How is EDB to know whether to transfer it or not ? I
>guess we could do it only if it is referenced in an index.

That actually make more sense than my idea (surprise surprise). I was just thinking its easier (for me) to transfer them all and then delete the ones I didn't want

Roy Lambert