From 56e374776dfc5e6d371a27e24dc2646c844f4c0f Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Thu, 25 Aug 2011 09:40:52 -0400 Subject: [PATCH] and lets use the right method name here... --- lib/sqlalchemy/orm/events.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/sqlalchemy/orm/events.py b/lib/sqlalchemy/orm/events.py index 913d764dac..714cc92452 100644 --- a/lib/sqlalchemy/orm/events.py +++ b/lib/sqlalchemy/orm/events.py @@ -586,7 +586,7 @@ class MapperEvents(event.Events): should any other ORM-based operation such as :class:`.Session.add` take place here. Attribute changes on objects that were already flushed will be discarded, and changes to the flush - plan will also not take place. Use :meth:`.Session.before_flush` + plan will also not take place. Use :meth:`.SessionEvents.before_flush` to change the flush plan on flush. :param mapper: the :class:`.Mapper` which is the target @@ -702,7 +702,7 @@ class MapperEvents(event.Events): should any other ORM-based operation such as :class:`.Session.add` take place here. Attribute changes on objects that were already flushed will be discarded, and changes to the flush - plan will also not take place. Use :meth:`.Session.before_flush` + plan will also not take place. Use :meth:`.SessionEvents.before_flush` to change the flush plan on flush. :param mapper: the :class:`.Mapper` which is the target @@ -770,7 +770,7 @@ class MapperEvents(event.Events): should any other ORM-based operation such as :class:`.Session.add` take place here. Attribute changes on objects that were already flushed will be discarded, and changes to the flush - plan will also not take place. Use :meth:`.Session.before_flush` + plan will also not take place. Use :meth:`.SessionEvents.before_flush` to change the flush plan on flush. :param mapper: the :class:`.Mapper` which is the target -- 2.47.3