Tim

I know that many times it will not be possible but can we have advance warning if the development of ElevateDB is going to break existing code, especially when it was well established in DBISAM (sorry to bring that name up in conjunction with ElevateDB). eg Its no longer possible to edit canned result sets.

Not sure if my intent is to think about it and work round it beforehand or just scream loudly I also know you, if anything like me, can change your mind between 0 and lots of times as development continues.

Right off to try and change a couple of components that relied on that behaviour

Roy Lambert

Roy,

<< I know that many times it will not be possible but can we have advance
warning if the development of ElevateDB is going to break existing code,
especially when it was well established in DBISAM (sorry to bring that name
up in conjunction with ElevateDB). eg Its no longer possible to edit canned
result sets.

Not sure if my intent is to think about it and work round it beforehand or
just scream loudly I also know you, if anything like me, can change your
mind between 0 and lots of times as development continues.

Right off to try and change a couple of components that relied on that
behaviour >>

Well, we do send you an email with the release notes, so it's not like
you're installing the latest version without knowing that the change is in
there.  I just don't know if it's feasible for me right now to run every
change by the newsgroups.  In many cases it's a huge drain on my time.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

I wasn't complaining, or in this case, asking to put it to a vote, just wondering if when you have plans of that nature they can be posted. Thinking about it, not posting in advance will probably save a lot of your (and everyone elses) time.


Roy Lambert

Roy,

<< I wasn't complaining, or in this case, asking to put it to a vote, just
wondering if when you have plans of that nature they can be posted. Thinking
about it, not posting in advance will probably save a lot of your (and
everyone elses) time. >>

I try to do it for big things, but because this particular "feature" is
easily replaced with a CREATE TABLE AS or CREATE TEMPORARY TABLE AS
statement, I thought that it really wasn't worth getting everyone involved.

Also, many questions or queries that we received with DBISAM were "Why do
you allow someone to edit a result set when the edits don't go anywhere ?".


--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>I try to do it for big things, but because this particular "feature" is
>easily replaced with a CREATE TABLE AS or CREATE TEMPORARY TABLE AS
>statement, I thought that it really wasn't worth getting everyone involved.

Having just done it. All I have to say is HA!

And to qualify that. It was made worse because its for a component settings editor so running in the IDE and I decided to use an in memory table and then because I'm getting field lists for tables in use selected databases I had to switch databases so my "simple" change involved creating and dropping a database, creating and dropping the in memory table and in between switching the database.information database to point to the right one.

>Also, many questions or queries that we received with DBISAM were "Why do
>you allow someone to edit a result set when the edits don't go anywhere ?".
>

Oh yes I remember reading quite a few of those.

Roy Lambert

Roy,

<< Having just done it. All I have to say is HA!

And to qualify that. It was made worse because its for a component settings
editor so running in the IDE and I decided to use an in memory table and
then because I'm getting field lists for tables in use selected databases I
had to switch databases so my "simple" change involved creating and dropping
a database, creating and dropping the in memory table and in between
switching the database.information database to point to the right one. >>

Yes, but none of the above has anything to do with editing an insensitive
result set.   The CREATE TABLE AS statement can be run exactly in-place for
a SELECT statement.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>Yes, but none of the above has anything to do with editing an insensitive
>result set. The CREATE TABLE AS statement can be run exactly in-place for
>a SELECT statement.

Not quite. Technically, if you're creating the table once and in the same database as the source table you're right. However, I wouldn't want to do this in any of the configuration databases, and I don't think ElevateDB will/should allow this. Therefore, extra step 1 - create database to hold temporary table. The contents of this tale (fields within a table) change when a different table is selected so extra step 2 - drop table if it exists so a new version can be created. Since I don't want the database when I've finished editing the parameters for the component extra step 3 - drop database.

So I end up with an extra query component, an extra table component and a few extra steps. So yes the actual select statement differs by "CREATE TABLE AS" and a couple of brackets BUT there's a fair bit of extra stuff round it.

Roy Lambert

Roy,

<< Not quite. Technically, if you're creating the table once and in the same
database as the source table you're right. However, I wouldn't want to do
this in any of the configuration databases, and I don't think ElevateDB
will/should allow this. >>

EDB doesn't allow it.

<< Therefore, extra step 1 - create database to hold temporary table. The
contents of this tale (fields within a table) change when a different table
is selected so extra step 2 - drop table if it exists so a new version can
be created. Since I don't want the database when I've finished editing the
parameters for the component extra step 3 - drop database. >>

Okay, now I understand what you were describing.  However, the desire to
have editable result sets for Configuration database and/or Information
schema queries will be relatively rare, I believe.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>Okay, now I understand what you were describing. However, the desire to
>have editable result sets for Configuration database and/or Information
>schema queries will be relatively rare, I believe.

Probably. BUT since the ORDER BY clause isn't respected add another extra step - create index

Roy Lambert