Re: [flask] Feature request - signals in Flask-SQLAlchemy
- From:
- Armin Ronacher
- Date:
- 2010-08-01 @ 05:36
Sounds good. Will implement that. Can you file an issue so it does not get lost?
Regards,
Armin
(sent from a handheld device)
On 01.08.2010, at 01:51, Dan Jacob <danjac354@gmail.com> wrote:
> As we now have signals in Flask (through blinker) it would be a good
> idea to be able to use these in Flask-SQLAlchemy. This could be done
> through a mapper extension:
>
>
http://www.sqlalchemy.org/docs/reference/orm/interfaces.html#sqlalchemy.orm.interfaces.MapperExtension
>
> Typical signals could be e.g after_delete, before_insert etc. fired by
> the respective extension event.
>
> This would have a number of uses, for example updating a denormalized
> field, logging, sending an email, etc.
Re: [flask] Feature request - signals in Flask-SQLAlchemy
- From:
- Stephane Wirtel
- Date:
- 2010-08-01 @ 00:43
+1
Written from my iPhone !
Le 1 août 2010 à 01:51, Dan Jacob <danjac354@gmail.com> a écrit :
> As we now have signals in Flask (through blinker) it would be a good
> idea to be able to use these in Flask-SQLAlchemy. This could be done
> through a mapper extension:
>
>
http://www.sqlalchemy.org/docs/reference/orm/interfaces.html#sqlalchemy.orm.interfaces.MapperExtension
>
> Typical signals could be e.g after_delete, before_insert etc. fired by
> the respective extension event.
>
> This would have a number of uses, for example updating a denormalized
> field, logging, sending an email, etc.
Re: [flask] Feature request - signals in Flask-SQLAlchemy
- From:
- heww0205
- Date:
- 2010-08-01 @ 03:22
A good idea.
2010/8/1 Stephane Wirtel <stephane@wirtel.be>
> +1
>
> Written from my iPhone !
>
> Le 1 août 2010 à 01:51, Dan Jacob <danjac354@gmail.com> a écrit :
>
> > As we now have signals in Flask (through blinker) it would be a good
> > idea to be able to use these in Flask-SQLAlchemy. This could be done
> > through a mapper extension:
> >
> >
>
http://www.sqlalchemy.org/docs/reference/orm/interfaces.html#sqlalchemy.orm.interfaces.MapperExtension
> >
> > Typical signals could be e.g after_delete, before_insert etc. fired by
> > the respective extension event.
> >
> > This would have a number of uses, for example updating a denormalized
> > field, logging, sending an email, etc.
>