Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread Manual & DBISAM migration
Mon, Dec 31 2007 12:11 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Can we have a section in the manual for gotchas and significant SQL changes please for those of us trading the painful path from DBISAM.

My favourites so far from today's selection.

SELECT INTO -> CREATE TABLE AS (especially INTO a memory table)
UPDATE with JOINS
Banned characters (Company:Project was a valid index name in DBISAM but the : isn't allowed in ElevateDB)

I know all the stuff is in the manual somewhere but, especially for the sql it would be nice to have a single location where I could lookup the old and see the new.

Roy Lambert
Mon, Dec 31 2007 7:25 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< Can we have a section in the manual for gotchas and significant SQL
changes please for those of us trading the painful path from DBISAM. >>

That's what this is here:

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

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Jan 1 2008 6:59 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


I gave  you the benefit of my doubt and had a look at the link and its not what I'm suggesting, it is a useful part of the technical reference as to what has changed.

I may still be wrong but I'd like to see you, or anyone, lookup on one of the linked pages and find

1. The fact that : is no longer allowed in index names
2. The equivalent to SELECT INTO
3. How to rephrase a query that used joins in a DELETE statement

simply and without having to reference several other pages to find the answer.

Roy Lambert
Tue, Jan 1 2008 12:59 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< I gave you the benefit of my doubt and had a look at the link and its not
what I'm suggesting, it is a useful part of the technical reference as to
what has changed. >>

But it includes all of the information that you're wanting, except for the
identifier names, which aren't mentioned in the migration part of the
manual.  However, it is mentioned here:

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

in great detail.

<< 1. The fact that : is no longer allowed in index names
2. The equivalent to SELECT INTO
3. How to rephrase a query that used joins in a DELETE statement

simply and without having to reference several other pages to find the
answer. >>

I'm sorry Roy, but you're expecting too much here.   There's no way I could
possibly cover every possible question in its exact form that someone may
ask during the migration.  The only way to cover it all is via a reference
to what has changed and how to deal with that change, which is what has been
done.

SELECT INTO:

"The INTO clause is no longer supported. ElevateDB uses the standard SQL
CREATE TABLE AS clause to create a table using a query expression."  (with a
link to the CREATE TABLE syntax)

DELETE with joins:

"The FROM clause is no longer supported. ElevateDB can use correlated
sub-queries in the WHERE clause."

Terms like "correlated" are industry-standard SQL terms that mean specific
things.  You can find information on what a correlated query is just about
anywhere:

http://www.google.com/search?q=correlated+query&rls=com.microsoft:en-us:IE-SearchBox&ie=UTF-8&oe=UTF-8&sourceid=ie7&rlz=1I7GGIC

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Jan 2 2008 3:40 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


>But it includes all of the information that you're wanting, except for the
>identifier names, which aren't mentioned in the migration part of the
>manual. However, it is mentioned here:

This one we have to differ on.

>I'm sorry Roy, but you're expecting too much here. There's no way I could
>possibly cover every possible question in its exact form that someone may
>ask during the migration. The only way to cover it all is via a reference
>to what has changed and how to deal with that change, which is what has been
>done.

I accept that unless you forget sleep, eating and preferably clone yourself a few times.

How about a wiki - I don't, but I'm sure someone on this newsgroup must have experience with them?

>Terms like "correlated" are industry-standard SQL terms that mean specific
>things. You can find information on what a correlated query is just about
>anywhere:
>
>http://www.google.com/search?q=correlated+query&rls=com.microsoft:en-us:IE-SearchBox&ie=UTF-8&oe=UTF-8&sourceid=ie7&rlz=1I7GGIC

I'm sure that in a couple of years I'll understand industry-standard SQL terms, at the moment I, and I suspect a largish number of your customers, don't.

I did try searching the web and did find a lot of bumph. Most of it was beyond my comprehension either from the way it was written, the examples given, or the fact that it constantly referred to implementation specific features (they might not have been but at my state of knowledge they seem to be).

I'll keep soldiering on and building up my personal knowledge base. In a couple of years I'll know it all (or at least all I need).

Roy Lambert
Wed, Jan 2 2008 9:04 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Maybe what I need is a better book on SQL. The two I have are at best SQL99. Can you recommend a reasonably priced one that covers SQL2003 and is readable by a non-expert?

Roy Lambert

ps it would be smashing if it covered the ElevateDB exceptions and enhancements too <vbg>
Wed, Jan 2 2008 4:07 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< Maybe what I need is a better book on SQL. The two I have are at best
SQL99. Can you recommend a reasonably priced one that covers SQL2003 and is
readable by a non-expert? >>

An SQL99 book should cover the majority of the ElevateDB implementation, if
not all of it.  A lot of 2003 was object and XML enhancements or syntactic
sugar additions.

The best books on SQL are those by Jim Melton.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Jan 3 2008 3:41 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

>or syntactic
>sugar additions.

I'm diabetic - am I allowed this?

Roy Lambert
Image