It seems that any table definition gets augmented with an adiitional "RowID"
system column.

When I define a simple table like:

create table test (col1 integer);

and query that table:

select * from test;

I'd expect to get a result with the single column "col1", and not a result
containing some weird system generated columns ("RowID").

This EleveateDB behavior is not only non-standard, it's totally proprietary
in the RDBMS world.

Suggestion - if you for some reason need this system column, make it hidden
and ivokable by a system function (e.g. RowID):

select RowID, *
from test;

Ole Willy Tuv

I *totally* second that!


Michael

Ole Willy Tuv wrote:
> It seems that any table definition gets augmented with an adiitional "RowID"
> system column.
>
> When I define a simple table like:
>
> create table test (col1 integer);
>
> and query that table:
>
> select * from test;
>
> I'd expect to get a result with the single column "col1", and not a result
> containing some weird system generated columns ("RowID").
>
> This EleveateDB behavior is not only non-standard, it's totally proprietary
> in the RDBMS world.
>
> Suggestion - if you for some reason need this system column, make it hidden
> and ivokable by a system function (e.g. RowID):
>
> select RowID, *
> from test;
>
> Ole Willy Tuv
>
>

> When I define a simple table like:
>
> create table test (col1 integer);
>
> and query that table:
>
> select * from test;
>
> I'd expect to get a result with the single column "col1", and not a result
> containing some weird system generated columns ("RowID").

Likewise, when I open the table in the ElevateDB Manager or reverse-enigneer
it to SQL, I'd expect to see my original table definition, and not any
system generated columns.

Ole

Ole,

<< It seems that any table definition gets augmented with an adiitional
"RowID" system column. >>

Yes it does.  This was mentioned months ago here on the newsgroups.  It is
not new.  Making it hidden won't work because then we'll have the same
problems we did with DBISAM in terms of Locate and FindKey not working on
the RowID column.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

>
> Yes it does.  This was mentioned months ago here on the newsgroups.
> It is not new.  Making it hidden won't work because then we'll have
> the same problems we did with DBISAM in terms of Locate and FindKey
> not working on the RowID column.


It works for me. I use GUIDS for primrary keys in all tables in order
to make merging of databases more robust.  Having the RowID visible
saves me a step as I would typically add an autoinc field anyway to
make the table records more readable by end-user administrators as well
as for me when scanning table data.

--
David Farrell-Garcia
Whidbey Island Software, LLC