[OGo-Developer] Changes to trunk, Testing

[Adam Tauno Williams]

>I've done a few changes to the way insert/update operations work.
> First of all primary key batches now work again, don't know how they  
> got lost (the SQL sequences reserves a batch of 10 keys per  
> invocation, so far we only used one of them resulting in wasted key  
> space ...).
> Next I changed the way object_version, last_modified, etc fields are  
> updated, and I added those to a few classes which didn't have them  
> before (eg docs, notes and projects).

Excellent.

> Finally I plan to enhance the database schema for 5.4. Mostly:
> - notes/documents attached to company records

Awesome!

> - parent_id in project table

Hierarchical projects?

> - a few other minor things

What about "Enh: Add ability to create hierarchies of depenedent tasks"
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1089
Jobs already have a parent_id, but that value seems to be treated oddly
resulting from some relic code.
(a) The current field could be recycled somehow and the relic code
removed
(b) It could be solved with object links
(c) Or a field could be added: "blocks_job_id"

> If someone has wishes for additional fields, shout now ;-) This isn't  
> committed yet.

I've been thinking about -
Enh: notification mails on uploads and document releases
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=229

I was imagining just storing a CSV list of users in a property,  perhaps
adding an add-me/remove-me button to the UI.  But if you are in a schema
changing mood then perhaps you can envision something more elegant.
Seems like it could be generalized to support change notification on
just about anything;  just store obj_id, company_id [account id].
Changes invoke a notification e-mail to email1 of company_id.

> Anyways, because some core stuff has changed some testing would be  
> good. Especially creating various kinds of objects.

Will do, let us know when it is committed.