That seems to be a good idea... I would love to see this in the next
release.
On Apr 8, 9:41 pm, Thadeus Burgess <thade...@thadeusb.com> wrote:
> Ive sent emails on the list twice, and one email to you personally
> about this. I have not implemented it since it never received any
> feedback.
>
> There will be a 'pre' and 'post' of 'select', 'insert', 'update',
> 'delete', separated by an underscore.
>
> The dal will maintain a list of functions for each of these. The
> function will be executed in order of assignment.
>
> So
>
> db.register('post_delete', copyRecordFunc)
> db.register('post_delete', notifyByEmail)
>
> In the dal.py it will look like
>
> results = self._cursor.execute('blah')
> for f in self.signals['post_delete']:
> f(results)
>
> -Thadeus
>
> On Thu, Apr 8, 2010 at 10:59 AM, mdipierro <mdipie...@cs.depaul.edu> wrote:
> > y have missed or forgotten about this. I would be in favor
> > of this but I would like to see a complete naming scheme and
> > understand how do you handle the case when two functions are regitered
> > for the same function. How do you han
