the "mutable" flag has been removed, for one thing. For another, when you change the value of the thing you're pickling, that's a plain Python object, like a list or a dictionary. It has no way of emitting an event on change unless you've designed it to do so.
On Apr 11, 2013, at 12:28 PM, rohit <rohit0...@gmail.com> wrote: > I think SQL Alchemy should raise some exception when a code tries to change > the value of a Pickle type attribute when mutable = False. > Reason for this is that user has accepted an attribute to be immutable and > still trying to change the value. > Can anyone explain the reason for not having so ? > > http://docs.sqlalchemy.org/en/rel_0_8/core/types.html#sqlalchemy.types.PickleType > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
