Early this morning [log in to unmask]:

> <<(9)    Allow tracking files to be associated with an IMAGE
> database (all associated files;  such as schemas, 3rd-party
> indexes, etc.).>>
>
> Schemas: does this refer to the file that would be equated
> to DBSTEXT?

Yes;  at least AFAIR all discussion I've been involved in says
so...   :-)

> ....  If so, there would have to be some clear convention
> (already in use in many places):
> dbnameSC.data_base_group.

There might be a few variations that would all work:

(1)   Use just dbnameXX.    This would default to looking in
usual order:  GROUP.ACCOUNT;  then PUB.ACCOUNT.

(2)   dbnameXX.GROUP.    Would look in a particular group;
in whatever account the database and schema were in.

(3)   dbnameXX.GROUP.ACCOUNT.    Would "lock" the
schema file into a specific group / account (this is what
ALLBASE does with the DBE log files (and I wish I had
options like (1) and (2) above for said ALLBASE log files) ).

First would allow copying databases and associated schema
to different groups and different accounts.  Second would
allow copying database and schema to a specific group in
more than one account.  Third would "lock" the schema to a
particular group and account (don't know that anyone would
want to do that;  but they *might* want to)....


> ....  Also, the two data base maintence tools would have to
> come on board and default (with override being possible) to
> this convention for decompiling or reporting a schema.

I don't know that the database tools would necessarily do
anything with the schema file;  other than check for EXIST
or NOT_EXIST (although they certainly could do more if they
wanted to).  For *generating* a schema, expect the tools
would want to continue to get that right out of the root file....
But the tools vendors will have to speak for themselves...  :-)


> ......Is this ballot suggestion meant to deal with attached
> ALLBASE DBE files?

I would pretty clearly think not;  i.e.:  A site may have more
than one TurboIMAGE database ATTACHed to one DBE.
My read of this enhancement is all files which are *directly*
associated with ONE particular TurboIMAGE database...

Hope all will pardon my brief response (or maybe most are
applauding...)  .....  I'm closing in on finish;  getting
TurboIMAGE and HPSQL SIGImage/SQL ballots up on the
web;  plus unrelated local panic;  got to run...

Ken Sletten