[OGo-Developer] Changes to trunk, Testing

[Adam Tauno Williams]

--=-u7ZruEVr7k2ilxxNwAFO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> >> 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=3D229
> > I was imagining just storing a CSV list of users in a property,  =20
> > perhaps
> > adding an add-me/remove-me button to the UI.  But if you are in a =20
> > 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.
> Hm, a global change notification thing is a pretty smart idea. It =20
> would allow for per-user/per-object/per-action notifications. Need to =20
> think about that.
> Might also be a more elegant solution for Sebastians request.
> I wonder whether we could again use obj_link for that (type =20
> notification with the notification object pointing to the user). =20
> Though maybe this really deserves an own table.

Since the table would need to be check every time there is a set:: or
update:: it seems like a stand-alone table might be faster, that only
contains the notification information.  Although a partial index on the
obj_link table would really accomplish the same thing - but fancy things
like that aren't supported in MySQL or SQLite.

--=-u7ZruEVr7k2ilxxNwAFO
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBGXBXXLRePpNle04MRAgKgAJsFjBy3fADcQrxlaaiOihYUpw5zegCeNCmw
isfcMMveyCpuwpbDJ72VVU8=
=NnjA
-----END PGP SIGNATURE-----

--=-u7ZruEVr7k2ilxxNwAFO--