I have not used any major DBMS with a "catalog". What does ElevateDB having
this new feature really mean to me and my applications? Is it something I
would enhance and change and distribute with my application changes or
basically the same as a server configuration file? Can it be created,
repaired or rebuilt from existing tables?

Tim, if you are answering this, please don't waste too much time on my
newbie question - I know you are very busy. I just thought others might be
able to point me to an online discussion of something similar.

-Johnnie

Johnnie,

<< I have not used any major DBMS with a "catalog". What does ElevateDB
having this new feature really mean to me and my applications? Is it
something I would enhance and change and distribute with my application
changes or basically the same as a server configuration file? Can it be
created, repaired or rebuilt from existing tables? >>

It defines all objects in a given database, therefore it is the bible that
determines how everything is structured.  You can't rebuild it from tables
because tables don't contain metadata, only the catalog does.  Tables with a
valid catalog are useless since EDB has no way of knowing what columns are
in the table, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:2B5A4C22-E6EE-4917-B22C-96290196C685@news.elevatesoft.com...
> Johnnie,
>
> << I have not used any major DBMS with a "catalog". What does ElevateDB
> having this new feature really mean to me and my applications? Is it
> something I would enhance and change and distribute with my application
> changes or basically the same as a server configuration file? Can it be
> created, repaired or rebuilt from existing tables? >>
>
> It defines all objects in a given database, therefore it is the bible that
> determines how everything is structured.  You can't rebuild it from tables
> because tables don't contain metadata, only the catalog does.  Tables with
> a valid catalog are useless since EDB has no way of knowing what columns
> are in the table, etc.

OK, I get it. Thanks. I assume your last statement was a typo and should be
"Tables WITHOUT a valid catalog ..."

Does that means the only use for *distributing* a catalog file with an
application would be for the initial creation of a database? One still needs
to follow the DBISAM methods when altering tables and indexes, correct?

Happy Holidays! Be sure to take some time off.

-Johnnie

Johnnie,

<< OK, I get it. Thanks. I assume your last statement was a typo and should
be "Tables WITHOUT a valid catalog ..." >>

Yes, sorry.

<< Does that means the only use for *distributing* a catalog file with an
application would be for the initial creation of a database? One still needs
to follow the DBISAM methods when altering tables and indexes, correct? >>

Distributing a catalog right now without the matching configuration file
won't work.  This has been the basic discussion going on regarding the
linkage between the two.

<< Happy Holidays! Be sure to take some time off. >>

I will, thanks.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Johnnie Norsworthy" <jln206@verizon.net> wrote in message
news:B2953762-96F7-4ACB-8E50-4805925DF871@news.elevatesoft.com...
> I have not used any major DBMS with a "catalog".

I'm not sure there is any "major DBMS" without a catalog.

Here's a link to an article with some good info about catalogs:
http://www.dbazine.com/db2/db2-disarticles/pelzer4

-- Herb Sitz