I'm thinking of a different way to arrange the example demos to help
new-comers struggling with back ends. (No change to the simple-blog
though).
At the moment the variations by API provide no examples of serious
object storage:
weblocks-demo does use an object model, exploiting inheritance
(employee - person) and composition (address - person) but with only
two simple storage options. One is a memory store used in the online
demo, and the other is a simple persistent XML store, which requires a
bit of hacking to get working.
weblocks-clsql-demo will talk to any clsql back end, but only
implements a relational model - no inheritance (hence no 'person'
class), and composition requires foreign keys.
weblocks-elephant-demo is relational like weblocks-clsql-demo, but
with the elephant API
................
Given that both clsql and elephant can be used with object databases,
I'd propose the following set instead:
1. weblocks-memory-demo. The current on-line demo with data in
hunchentoot sessions.
2. weblocks-object-demo. The store could contain variants for
XML simple persistence via cl-prevalence
clsql with postgresql (and postgresql-sockets)
elephant with postgresql
elephant with berkely db
... and we should be able to add allegro cache at some stage
3. weblocks-relational-demo. The store could initially contain
variants for
clsql with mysql
clsql with postgresql (and postgresql-sockets)
Each of the three would have different code for models, stores and
views, but within each one the code should be the same whatever the
back end. The configs necessary could easily be covered in the
README. Sample scripts could also be included for establishing
databases from class definitions and the sample data.
I'd do the initial work - I need the practice. Any suggestions or
objections?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
