Assaph Mehr wrote:

>Oh well, time to read the docs I guess :-)
>
>  
>
Feel free to keep asking questions.  I just mentioned the examples in 
the distribution in case you wanted to see "record classes" in action.

>So how are many-to-many relationshops handled (e.g. authors and books)?
>
>  
>
Hmm, let me think about this.  I guess I would create an author table, a 
book table, and a book_author table in the middle that would link the 
two.  I think that would work for a many-to-many.


>Also, how well does KB deal with "schema" changes between revisions? I
>mean a new class version vs old data-store - how do I handle old
>record data vs. new fields?
>  
>
You are free to modify the record class as much as you want.  KirbyBase 
is going to pass in the field values to the #kb_create method.  After 
that, it is up to you to do with them what you will.

You can also do an #add_table_column and #drop_table_column to 
add/delete fields from the table after it is created.

Jamey