Tim

I finally got round to printing out the sql pdf. That was a major task in its own right. I printed in reverse order two pages per sheet (just to save paper) and it stopped after a couple of hundred pages. Then the mismatch between on screen and printed page numbers gave great entertainment.

I apologise if the answers to some of the questions are obvious, or easily obtainable via testing/experimentation.

Questions

General
What is the organisation within the sections? I don't really care just wondering. Its not alphabetic so I just wonder if there is any significance to the order that I should be aware of.

6.2
What does just JOIN expand to - I think its INNER JOIN is that right?

7.4
Is it possible to have more than one WITH RETURN? If so how are they accessed one the script has been run?

7.15
Reading I get the impression this is only allowed in JOBS. Is this right?

11.5
What basis is WEEK calculated on? Question prompted by a thread in the CodeGear ngs

16.8
The opening statement
<<Returns whether or not a result set cursor is sensitive to changes by other sessions or not>>
I'm confused by the reference to other sessions. I thought SENSITIVE = can be changed not SENSITIVE = cannot be changed regardless of session.


Suggestions
General
Where alternative versions of functions/commands exist (eg CHARACTER_LENGTH, CHAR_LENGTH) it might be a good idea to base the headings and example on the same version rather than switching.

7.4
I think it would be worthwhile stating at the top of the section that DECLARE's have to be at the front of the BEGIN..END block as well as an entry in deviations from the standard.

7.6
For the non-SQLers it might be worth pointing out the difference between Pascal and SQL statements - its caught me once so far.


Errata
7.10
WHILE - example good - definition not

10.2
You have CHARACTER_LENGTH, and LENGTH


Roy Lambert

Roy Lambert <roy.lambert@skynet.co.uk> wrote in
news:32B282A6-DEB3-4DD0-8F03-2AACBC78FEC2@news.elevatesoft.com:

Roy,

I think I may have one answer for you:

> 11.5
> What basis is WEEK calculated on? Question prompted by a thread in the
> CodeGear ngs

I read somewhere around here a few weeks ago that:

week 1 = the 1st week with a thursday in it

hope that fits!

--
Chris
(XP-Pro + Delphi 7 Architect + DBISAM 4.26 build 1 + EDB 1.07 build 2)

Chris


Thanks - it could have been here. I thought it was CodeGear but might well be wrong.

Roy Lambert

Roy,

<< I finally got round to printing out the sql pdf. That was a major task in
its own right. I printed in reverse order two pages per sheet (just to save
paper) and it stopped after a couple of hundred pages. Then the mismatch
between on screen and printed page numbers gave great entertainment. >>

Unfortunately we can't control how Adobe numbers the pages during printing.

<< What is the organisation within the sections? I don't really care just
wondering. Its not alphabetic so I just wonder if there is any significance
to the order that I should be aware of. >>

If you're referring to the SQL manual - it is organized according to the
level of information being presented, basic to advanced/reference.

<< What does just JOIN expand to - I think its INNER JOIN is that right? >>

Yes, it's standard SQL - JOIN is short-hand for an INNER JOIN.

<< Is it possible to have more than one WITH RETURN? >>

No.  EDB does not support returning multiple result sets.

<< Reading I get the impression this is only allowed in JOBS. Is this right?
>>

No, you can use it in scripts also.

<< What basis is WEEK calculated on? Question prompted by a thread in the
CodeGear ngs >>

ISO 8601 week calculation:

http://en.wikipedia.org/wiki/ISO_8601

<< The opening statement
<<Returns whether or not a result set cursor is sensitive to changes by
other sessions or not>>
I'm confused by the reference to other sessions. I thought SENSITIVE = can
be changed not SENSITIVE = cannot be changed regardless of session. >>

With a SENSITIVE result set, the changes from other sessions can be seen by
the result set.  With an INSENSITIVE result set, the changes from other
sessions cannot be seen by the result set.

Per the referenced topic on that page:

http://www.elevatesoft.com/scripts/manual.dll?action=mantopic&id=edb1sql&category=0&topic=17

<< Where alternative versions of functions/commands exist (eg
CHARACTER_LENGTH, CHAR_LENGTH) it might be a good idea to base the headings
and example on the same version rather than switching. >>

One is just short-hand for the other.  We use the standard, complete name
for the reference.

<< 7.4
I think it would be worthwhile stating at the top of the section that
DECLARE's have to be at the front of the BEGIN..END block as well as an
entry in deviations from the standard. >>

Noted.

<< 7.6
For the non-SQLers it might be worth pointing out the difference between
Pascal and SQL statements - its caught me once so far. >>

I'll have to think about this.  This is a general SQL manual and is not just
for Delphi developers.

<< Errata
7.10
WHILE - example good - definition not >>

Got it.

<< 10.2
You have CHARACTER_LENGTH, and LENGTH >>

Got it.

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>Unfortunately we can't control how Adobe numbers the pages during printing.

I know - that was just a general moan. It took ages to fill the gap in the middle.

><< Is it possible to have more than one WITH RETURN? >>
>
>No. EDB does not support returning multiple result sets.

Possibly worth mentioning. When I get my current script sorted I must experiment and see how spectacularly I can get it to blow up

><< Reading I get the impression this is only allowed in JOBS. Is this right?
> >>
>
>No, you can use it in scripts also.

Definitely needs rewording then <<Use this statement in a job definition>>

Roy Lambert

Roy,

<< Possibly worth mentioning. When I get my current script sorted I must
experiment and see how spectacularly I can get it to blow up >>

You'll simply get a compilation error to the effect of:

duplicate result cursor declaration <CursorName> found

<< Definitely needs rewording then <<Use this statement in a job
definition>> >>

Yes, I know - scripts came after the fact and the docs weren't updated to
reflect that.

--
Tim Young
Elevate Software
www.elevatesoft.com