A notable limitation of CouchDB at present is that a user can either read all items in a database or none.  So, if users should not be able to see projects they are not involved in, you'll need a database per project.

There's no need to keep work logs in a different database than projects - that would limit the views you can create.

Sent from my Palm Pre

On Oct 14, 2010 3:21 PM, serapicos <serapicos....@gmail.com> wrote:

Hi,

i'm reading and trying couchdb and couchapp and i'm willing to build

an application for project tasks work logs, e.g., the app will have a

bunch of users assigned to projects through tasks.

Each users will log their work to the task assigned to him.

The project is created, the project tasks are created and assigned to

an user.

The user will see its tasks and will toogle between them (like play/

pause/stop) creating work logs in the way.

All i want is some suggestions for the couchdb/couchapp better way to

"model" this up:

1. one database for the users (or using the couchdb _users one)

2. one database for projects (and is properties)

3. one database for work logs or one database for each user work logs

Is there a way to connect all the databases in one couchapp? Or should

i do it all in just one database?

Any directions/suggestions will be appreciated!!!

Thanks in advance,

asousa

--

You received this message because you are subscribed to the Google Groups "CouchApp" group.

To post to this group, send email to couchapp@googlegroups.com.

To unsubscribe from this group, send email to couchapp+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/couchapp?hl=en.