Some initial thoughts (may be you have already considered them):
1) Page -6 (of pdf)
------------------------------
(a)
Windows syntax:
C:\> set DERBY_HOME=C:\derby
C:\> md DERBYDBS
C:\> chdir DERBYDBS
C:\> copy something.sql .
(I presume, the sql file is being copied from some dir under DERBY_HOME. In that case, the actual path to the source sql file is missing)
Same for the Linux steps
(b)
Can we name the file 'sample.sql' instead of 'something.sql'.
Also I am thinking will it be useful if this 'sample.sql' file can have statements of each type - Update, Delete, Primary Key, Foreign Key, Create/Select from Views etc. etc.with brief description using '--' comments ? It can help in familiarizing with commonly used SQL features in Derby. The same script can used in Activity 2 with the Derby client driver.
More comments as I proceed with my reading.
Regards,
Rajesh
On 3/8/06, Stanley Bradbury <
[EMAIL PROTECTED]> wrote:
Thanks for the chiming in on this..
Susan Cline wrote:
>--- Stanley Bradbury < [EMAIL PROTECTED]> wrote:
>
>[snip]
>
>
>>>>I've submitted Chapters 1 and 2 of the Work With Derby [WWD] document
>>>>for feedback. These sections are based on the version 1.1 proposal
>>>>submitted last week. You can download the formatted PDF document for
>>>>review and comment using the following URL.
>>>>
>>>> http://issues.apache.org/jira/secure/attachment/12323814/workingwithderby0306.pdf
>>>>
>>>>
>
>[snip]
>
>
>
>>>(4) pdf page 6 (printed page 4), step 8 shows the "shutdown=true"
>>>command. Since Activity 1 shows embedded use and "exit" in an embedded
>>>environment automatically performs that shutdown=true
>>>( http://db.apache.org/derby/docs/dev/tools/rtoolsijcomref33358.html), I
>>>wonder if you could delay showing that syntax and the error that gets
>>>produced until the next activity with the client driver.
>>>
>>>
>>>
>>>
>>>
>> >>> You are correct that this could be introduced in activity 3 (JDBC
>>with the embedded driver). There are two reasons I chose to place the
>>topic here:
>>1) It is a counter point to the item in the 'Summary' of the next
>>activity, outline point:
>> >> Best practice - shutdown the server do not shutdown the database
>>from a client
>>2) I believe that introducing concepts a few at a time across the
>>activities is better than creating a 'dense' topic by lumping everything
>>into one activity (in this case Activity3).
>> >>> I am leaning towards deferring introducing 'shutdown' until
>>Activity 3 since IJ does properly automate the process. The recent
>>revision of WWD does take advantage of the automations provided by
>>derbygo.jar and IJ. I would like to hear some other opinions on this if
>>we are to keep the document as-is.
>>
>>
>>
>
>Hi Stan,
>
>I think it would be nice to defer the shutdown=true to Activity 3. It would make the output for
>Activity Sequence 1 look a little bit cleaner and be a little bit kinder, gentler, introduction to
>Derby :-)
>
>Susan
>
>
>
