Hi everyone,

As a year-old CakePHP user (by the way : huge congrats to the core
team for keeping up such a pretty framework!) I'm considering to
replace MySQL by CouchDB. I had a dream where some unpredictable data
wouldn't require ugly schemas :)

So far I tried gwoo's datasource (http://bin.cakephp.org/view/
925615535 - see also the original topic [1])
This is a good start but it assumes that a couchDB database is the
counterpart of MySQL tables. I don't think so, as it's usual in
CouchDB to put a "type" field in documents : then the counterpart of
the table is rather a couch view (or sometimes show or list) which
picks up document sets. A CouchDB view sound like a good counterpart
to find('all', ...)

I tried to rewrite a datasource (if needed I can publish it on cakebin
today), keeping in mind that it would be tied to a single couchdb
database. BUT I found out that schemas are deeply implemented in the
Model class :/ so Cake started to call my source's listSources,
describe and column methods. Of course I couldn't implement these
methods as my DB doesn't have schemas... I tried to set useTable to
false in the Model but then it won't save anything.

So I'm stuck between a normal CouchDB use (a single DB for my whole
app + calls to views in mind) which doesn't seem cake-friendly and a
working datasource that puts some constraints on DB design.
That's why I would like to discuss it here. Any comments are welcome!


Martin

[1] original topic about cake+couch :
http://groups.google.com/group/cake-php/browse_thread/thread/f0eaa55149d7ddb3/bff40dbc700171f9

Check out the new CakePHP Questions site http://cakeqs.org and help others with 
their CakePHP related questions.

You received this message because you are subscribed to the Google Groups 
"CakePHP" 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/cake-php?hl=en

To unsubscribe, reply using "remove me" as the subject.

Reply via email to