Hi,

I am just lost.
What is ElevateDB. I check the website and I found some information. But I
sounds to me as Dbisam 5.0.

What is new?
Is better?
Is faster?
Why should I swith to ElevateDB?
Can it be used with Delphi6?
What will happen to DBISAM?


Thanks
Andre

Andre

You can find this information in the  Product Information link at
www.elevatesoft.com

But, with simple answers:

> What is new?
A lot of things

> Is better?
Yes

> Is faster?
In some circunstances is faster

> Why should I swith to ElevateDB?
RI, catalog, speed, stored procedures, etc

> Can it be used with Delphi6?
Yes, like DBISAM

> What will happen to DBISAM?
As I know, DBISAM will live one year (at least)

Eduardo

Andre,

<< What is ElevateDB. I check the website and I found some information. But
I sounds to me as Dbisam 5.0. >>

It was originally planned as DBISAM 5, but it turned into a complete rewrite
and became ElevateDB.

<< What is new? >>

We don't have a detailed DBISAM <-> EDB comparison yet, but you can see for
yourself that quite a bit is new:

http://www.elevatesoft.com/edb_prodinfo.htm

<< Is better? >>

We think it is, which is why we wrote it.  However, you'll have to judge for
yourself based upon your needs.

<< Is faster? >>

Yes, in several areas - indexing performance and compression and BLOB
handling, which means that inserts, updates, and deletes as well as a host
of other items is much faster.

<< Why should I swith to ElevateDB? >>

That is something that you would need to determine based upon your own
needs.

<< Can it be used with Delphi6? >>

Yes.

<< What will happen to DBISAM? >>

Nothing.  It will continue to be sold and developed as a separate product.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:28265B7A-9EFC-4AA6-A8FC-285CCDA7EF82@news.elevatesoft.com...
>
> << What will happen to DBISAM? >>
>
> Nothing.  It will continue to be sold and developed as a separate product.

Do you mean there will be a DBISAM 5 or is it just bugfixes you talk about ?

Uffe,

<< Do you mean there will be a DBISAM 5 or is it just bugfixes you talk
about ? >>

It depends on how much time is needed for EDB.  If there's time and demand,
and enough new features, then we'll certainly consider a DBISAM 5.  However,
it won't duplicate any functionality that is in EDB such as RI, etc.  That
defeats the whole purpose of EDB.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

However, it won't duplicate any functionality that is in EDB such as RI, etc.  

Sorry - I missed something.  What is RI?

I have read what I can find but still am finding it difficult to grasp the real
differences.  The ability to Index on a New Field in a table seems to me to be a great
addition if I understand correctly.  It would be very helpful to get a simple list of the
really big differences - if possible?

Will it be possible to install both into Delphi 7 so that older projects will not need to
be updated immediately?  If not, how easy is the migration to EDB?  What will need to be
done other than data file conversion?  Will all the table objects have to be replaced
manually?

Regards - Peter

Peter

> Sorry - I missed something.  What is RI?
Referencial Integrity. It is a basic concept of database design. For
example: if you have two tables, table1 hold data from customers and table2
hold data from customers buying. You can´t delete any record from table1
that has related records in table2.

> I have read what I can find but still am finding it difficult to grasp the
> real
> differences.  The ability to Index on a New Field in a table seems to me
> to be a great
> addition if I understand correctly.  It would be very helpful to get a
> simple list of the
> really big differences - if possible?
As a programmer, I have to told you it is very hard. Since ElevateDB is a
completelly re-written database tool. Many bugs were fixed and a lot of new
features added. And the code base of engine was re-written to grow up much
more than DBISAM could go.

> Will it be possible to install both into Delphi 7 so that older projects
> will not need to
> be updated immediately?
Yes, ElevateDB has other component names

> If not, how easy is the migration to EDB?
It is not easy to answer your question but it depends on your style of
programming but it will be easy.

> What will need to be done other than data file conversion?
Check the *ALL* code. When the final version will release there are a
section (I hope) called "Changes from DBISAM 4 to ElevateDB" that explain
what you have to look closely.

> Will all the table objects have to be replaced manually?
Yes, but this is a pretty easy editing DFM and PAS with a simple editor.

Eduardo

Peter

>If not, how easy is the migration to EDB? What will need to be
>done other than data file conversion?

I'm still hoping the answer will be "easy" but I'm beginning to doubt it A lot depends on what exactly Tim does before the end of the month (eg reintroduce sql scripts), and I know he's reading, understanding and responding to concerns.

Switching the table and query components will be the trivial part (I can send you an applet to do it, or you can use GExperts) but I'm betting all sql will need scrutinising if not altering, tables will be less affected than queries. The biggest "pain" will be learning the new features and taking advantage of them or learning to avoid them

Roy Lambert

Peter,

<< Sorry - I missed something.  What is RI? >>

See Eduardo's response.  RI is implemented via primary and foreign keys.
For example, this table definition:

CREATE TABLE "Albums"
(
"Name" VARCHAR(30) COLLATE "ANSI_CI",
"Artist" VARCHAR(30) COLLATE "ANSI_CI" NOT NULL,
"Genre" VARCHAR(20) COLLATE "ANSI_CI" NOT NULL,
"Year" INTEGER NOT NULL,
"Label" VARCHAR(30) COLLATE "ANSI_CI" NOT NULL,
"Imported" BOOLEAN DEFAULT FALSE  NOT NULL,
"NumDiscs" INTEGER DEFAULT 1  NOT NULL,
"CoverArt" BLOB,
"Comments" CLOB COLLATE "ANSI_CI",
"PurchasedOn" DATE,
"PurchasePrice" DECIMAL(20,2),
CONSTRAINT "Name" PRIMARY KEY ("Name"),
CONSTRAINT "Artist" FOREIGN KEY ("Artist") REFERENCES "Artists" ("Name"),
CONSTRAINT "Genre" FOREIGN KEY ("Genre") REFERENCES "Genres" ("Name"),
CONSTRAINT "Label" FOREIGN KEY ("Label") REFERENCES "Labels" ("Name")
)
DESCRIPTION 'Contains CD albums in the collection'

Says that any value in the Artist, Genre, or Label columns must exist in the
tables designated in the FOREIGN KEY definition.  Furthermore, any rows in
those referenced tables cannot be deleted if there are any Albums rows that
reference them.

<< The ability to Index on a New Field in a table seems to me to be a great
addition if I understand correctly. >>

I'm not sure what you mean by this - Index on a New Field ?

<< It would be very helpful to get a simple list of the really big
differences - if possible? >>

We'll have something within the next week regarding this.

<< Will it be possible to install both into Delphi 7 so that older projects
will not need to be updated immediately? >>

Yes.

<< What will need to be done other than data file conversion? >>

Components and code, primarily switching any TDBISAMTable-based metadata
code (CreateTable, AlterTable, CreateIndex, etc.) to straight SQL execution.

<< Will all the table objects have to be replaced manually? >>

You can just use Alt-F12 in the Delphi IDE to open up a form as text and do
a search/replace on the DBISAM components.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy,

<< I'm still hoping the answer will be "easy" but I'm beginning to doubt it
A lot depends on what exactly Tim does before the end of the month (eg
reintroduce sql scripts), and I know he's reading, understanding and
responding to concerns. >>

Don't hold your breath.  I'm running out of time to implement new stuff
at this stage in the game.  Scripts will probably have to wait until after
the initial release.

--
Tim Young
Elevate Software
www.elevatesoft.com