Re: [documentation-dev] Base Guide needs writers

2007-10-29 Thread K. Morgan
Hi all,
  I've been wanting a chance to contribute, but hadn't found anything.  I've 
been trying to learn Base because my job involves databases and the experience 
might help me.  If I can get a little guidance on what to do, I'd love to write 
something for Base.
-Kate
  
Andrew Jensen [EMAIL PROTECTED] wrote:
  LOL

Can we just nominate someone and then hound them into submission?

On 10/28/07, Jean Hollis Weber wrote:
 I don't recall if I mentioned that one of the volunteers to write parts of
 the Base Guide has had to withdraw due to lack of time, so we are back to
 desperately seeking contributors.

 --Jean

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: [documentation-dev] Base Guide needs writers

2007-10-29 Thread Jean Hollis Weber
Kate, that's great! Please see my recent notes to David Michel and others 
about the location of the Base Guide outline, and pick something that 
interests you. It doesn't have to be an entire chapter to start with; one 
section of a chapter would be fine.


Or you could do some stand-alone how-to's on specific topics (taken from 
the outline) that could later be combined into the book by an editor 
(probably me). I'm now thinking that might be a good way to handle having 
several people working on the book. There is a sample database that 
everyone should use so the examples and discussion fit together.


Drew Jensen among others is available to help as needed with technical 
details and guidance about Base itself.


A good place for anyone to start is: after picking a topic (or a chapter) 
to write about, develop the outline for that chapter or topic more fully. 
Most of the book's outline is only a wish list of topics at the moment. 
By developing the outline I mean work out a series of headings, in the 
order they are intended to appear in the table of contents, preferably with 
a short paragraph under each heading, saying what you plan to include in 
that section. At this point you may need to do some research to know what 
to cover. Don't worry to much at this point about the wording of the 
headings; they can (and some surely will) change later. Try to get the 
sequence of topics worked out, but be aware that the sequence may change 
later too, as you do more research and discover that a different sequence 
explains the topics better. When you have a detailed outline of your topic 
or chapter (or at any stage while you're working on it), send it to this 
list or put it on the wiki or the OOoAuthors website and ask on this list 
for comments.


Of course, if you want to just leap in and start writing and organise it 
later, that can work too. Up to you.


--Jean


K. Morgan wrote:

Hi all,
  I've been wanting a chance to contribute, but hadn't found anything.  I've 
been trying to learn Base because my job involves databases and the experience 
might help me.  If I can get a little guidance on what to do, I'd love to write 
something for Base.
-Kate
  
Andrew Jensen [EMAIL PROTECTED] wrote:

  LOL

Can we just nominate someone and then hound them into submission?

On 10/28/07, Jean Hollis Weber wrote:

I don't recall if I mentioned that one of the volunteers to write parts of
the Base Guide has had to withdraw due to lack of time, so we are back to
desperately seeking contributors.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [documentation-dev] Base Guide needs writers

2007-10-28 Thread Andrew Jensen
LOL

Can we just nominate someone and then hound them into submission?

On 10/28/07, Jean Hollis Weber [EMAIL PROTECTED] wrote:
 I don't recall if I mentioned that one of the volunteers to write parts of
 the Base Guide has had to withdraw due to lack of time, so we are back to
 desperately seeking contributors.

 --Jean

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [documentation-dev] Base Guide

2007-09-28 Thread Andrew Jensen
arrrgh - I suppose it is a case of, I made the mess with the two
accounts and I have to live with it..oh well...who invented case
sensitivity anyway.

On 9/28/07, Jean Hollis Weber [EMAIL PROTECTED] wrote:
 Andrew Jensen wrote:
  [aside] I tried to log onto OOoAuthors with my drewjensen account. I
  can log on but it tells me I don't have sufficient rights to even look
  at my own stuff, let alone anything else..*chuckle*..the nerve. Could
  you help on that?

 You have two accounts. The one called DrewJensen has Author
 privileges. The one called drewjensen did not, but now does. I
 suspect that if you log in under the latter username, you may
 still not be able to access your own stuff -- if you created it
 under the other name.

 Cheers, Jean

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [documentation-dev] Base Guide

2007-09-28 Thread Jean Hollis Weber

Andrew Jensen wrote:

[aside] I tried to log onto OOoAuthors with my drewjensen account. I
can log on but it tells me I don't have sufficient rights to even look
at my own stuff, let alone anything else..*chuckle*..the nerve. Could
you help on that?


You have two accounts. The one called DrewJensen has Author 
privileges. The one called drewjensen did not, but now does. I 
suspect that if you log in under the latter username, you may 
still not be able to access your own stuff -- if you created it 
under the other name.


Cheers, Jean

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [documentation-dev] Base Guide (was: Mid-level base tutorial)

2007-09-28 Thread Andrew Jensen
Jean,

I'll take a look at merging the wiki and document and incorporating
the idea brought up here about 'How to choose the right engine' first
of the week.

[aside] I tried to log onto OOoAuthors with my drewjensen account. I
can log on but it tells me I don't have sufficient rights to even look
at my own stuff, let alone anything else..*chuckle*..the nerve. Could
you help on that?

On 9/27/07, Jean Hollis Weber [EMAIL PROTECTED] wrote:
 Good question. Would be best to update both. :-)

 If we are working on the Base Guide primarily through the
 OOoAuthors webiste (instead of the wiki, as for the tutorial), I
 guess the primary source for the Base Guide outline should be the
 file on the OOoAuthors website. OTOH, the wiki page might be
 easier to keep up to date.

 BTW, the file you refer to exists in two versions at the moment:
 an ODT file and a page on the website itself. All of this
 duplication is not a good idea, but I haven't had the energy to
 do anything to consolidate things. Please feel free to
 rationalise all of them yourself, if you want to.

 Gosh, what a long-winded answer. I probably need another cup of
 tea to wake up the old brain cells. :-)

 Cheers, Jean

 Andrew Jensen wrote:
  Your correct. That would be a good place for this, kind of the natural
  place I suppose.
 
  OK, which outline is being updated then...I am so easily confused
  sometimes...the file that you sent out or the wiki page?
 
  Drew
 
  On 9/27/07, Jean Hollis Weber [EMAIL PROTECTED] wrote:
  Joe Smith wrote:
  Are there any plans to include a section comparing, in practical terms,
  which database type to choose for some typical projects?
  [...]
  This is a critical choice that the current UI gives almost no help with.
  It then falls to written documentation to explain the concepts and
  assist in choosing the right one.
  This is a good topic to include in the Base Guide, which
  obviously will be rather more comprehensive than a tutorial.
  IIRC, the outline includes a section or chapter on planning.

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [documentation-dev] Base Guide

2007-09-28 Thread mcasanova
Hi Andrew!

Thank you very much for the Hsqldb manual and the links that you sent me.
They proved to be very useful. The site in Portuguese never opened in my
browser so I could not check it.

However, I was able to gather most of the information that I needed...
with a few exceptions; and I am hoping that you can fill in the gaps: Data
types are not defined in the Hsqldb manual but referred to the Java types
they map (pag. 115). I really just want to identify the number of bytes
they use and whether they are signed or not in order to determine their
range. For example, I understood that TINYINT was a 1 byte unsigned data
type with a range of 0-255. Yet the manual says -under the Types and
Arithmetic Operators heading- that TINYINT ranged from -128 to +127.
Ahhrg!

I also understand that NUMERIC and DECIMAL are interchangeable in Hsql
(which is the engine this tutorial will assume that the user is using) and
can hold very large numbers and that REAL, FLOAT and DOUBLE, also
interchangeable, handle better the divisions. Is this consistent with your
experience?

To simplify what I am asking from you, could you please review and
complete- the best you can- the following table? (I really hope that the
formatting holds!):

Numeric Type Variables: Used for storing numeric values

NameData type   No. of BytesSigned  Range
Boolean yes/no   1 bit  0 - 1
Tinyint Tiny Integer1 Byte  No  0 – 255
SmallintSmall Integer
Integer Integer
Bigint  Big integer
Numeric Number  no limit (1MB)
Decimal Decimal no limit (1MB)
RealReal
Float   Float
Double  Double

I have chosen to leave the size, precision and scale attributes for an
advanced tutorial. I am also going to assume that the lax operation mode
in the handling of variable types is on by default when using Hsql.

I appreciate your help!

Mariano


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]