Hi Drew, and thank you for sending me feedback. I really appreciate this.

I did notice the slanted quote signs and how text with them would
sometimes throw an error when I try to run it as a query. This did bother
me too, a lot, but wasn't sure of what was going on. That is why I wrote
the footnote in page 112. Now I see. It seems that OO.oWriter included
them automatically (and sometimes not). I will change this.

On the other hand and except for the SQL that composes the example
database, the philosophy of the tutorial is that all code snippets should
be typed and not copy and pasted. There is a reason for this:

Theories of cognition describe several levels of knowledge: to know about,
to understand, to apply... (to cite the earlier stages) and then there is
this idea I align with that suggests that knowledge is always tied to
action. I can describe how the little dots in a pentagram translate to
musical pitches and durations but you can't really apply that knowledge to
reading music until you have actually practiced coordinating their
rendition with playing an instrument. I want people to learn by doing. For
the same reason I'm not sure if I want to provide odb files.I do have many
odb files I wrote while researching this project so uploading some is not
a problem; but I really think that the tutorial gives enough detailed
information for the reader to produce his/her own, which is what I  really
want.

I made an exception with the code for the tables because it is introduced
before it is explained and because it's quite long and I didn't want to
create a major barrier so early (and even then I recommend the reader to
take the time and type them anyway). I provide this code in a separate txt
file because I did not want the problem of the slanted quotes or the
unrequested line breaks to appear and didn't know another way to do it.

The line breaks in the tutorial were decided by the application. I'm going
to check and see if a reader who is actually typing them would have enough
context to distinguish physical line breaks from logical ones. However, I
am open to arguments that recommend that I re-format the code anyway.

Again, thank you very much for your feedback.

Mariano.


> Hi Mariano,
>
> (First sorry if this email arrives twice...odd things with the computer
> today..)
>
> I have it downloaded and have begun reading.
>
> I used the .sql file you uploaded to create a Base file database -
> worked as a charm under 3.2 - 3.3 beta.
>
> Tried a few of the queries - hit a small problem.
>
> The document it using nice double quotes that need to be changed - and -
> there can be line break problems in copy/paste.
>
> So for instance looking at the example on page #136. If I copy / paste
> this into a query definition I get this:
>
> SELECT CONCAT( CONCAT( “Patient”.“Surname”, ', ' ), “Patient”.“First
>
> Name” ) AS “Patient Name”,
>
> “Phone Number”.“Number”,
>
> “Phone Number”.“Description”
>
> FROM “Patient”, “Phone Number”
>
> WHERE “Patient”.“ID Number” = “Phone Number”.“Patient ID”
>
> ORDER BY “Patient Name” ASC;
>
>
>
> *chuckling*...which the email list server might change again..
>
> OK the query fails for two reasons.
>
> 1 - the characters " and ” must be "
> 2 - A object name which, in this case "First Name", can not have break
> across lines.
>
> So to get the query to run I need this
>
> SELECT CONCAT( CONCAT( "Patient"."Surname", ', ' ), "Patient"."First Name"
> ) AS "Patient Name",
>
> "Phone Number"."Number",
>
> "Phone Number"."Description"
>
> FROM "Patient", "Phone Number"
>
> WHERE "Patient"."ID Number" = "Phone Number"."Patient ID"
>
> ORDER BY "Patient Name" ASC;
>
>
>
> or this,
>
> SELECT CONCAT( CONCAT( "Patient"."Surname", ', ' ),
>
> "Patient"."First Name" ) AS "Patient Name",
>
> "Phone Number"."Number",
>
> "Phone Number"."Description"
>
> FROM "Patient", "Phone Number"
>
> WHERE "Patient"."ID Number" = "Phone Number"."Patient ID"
>
> ORDER BY "Patient Name" ASC;
>
>
> perhaps.
>
> Other wise - It's reading very nicely..
>
> Question - will you be including any example data? or an ODB file even?
>
> Thanks
>
> Drew
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org
> For additional commands, e-mail: dev-h...@documentation.openoffice.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org
For additional commands, e-mail: dev-h...@documentation.openoffice.org

Reply via email to