From ce47a4d46cc5750d5d2f7429f7c1f56731054e97 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 12 Feb 2010 20:28:23 +0000 Subject: formatting --- lib/sqlalchemy/ext/serializer.py | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'lib/sqlalchemy/ext/serializer.py') diff --git a/lib/sqlalchemy/ext/serializer.py b/lib/sqlalchemy/ext/serializer.py index d40ccc9c6..354f28c59 100644 --- a/lib/sqlalchemy/ext/serializer.py +++ b/lib/sqlalchemy/ext/serializer.py @@ -33,13 +33,14 @@ The serializer module is only appropriate for query structures. It is not needed for: * instances of user-defined classes. These contain no references to engines, -sessions or expression constructs in the typical case and can be serialized directly. + sessions or expression constructs in the typical case and can be serialized directly. + * Table metadata that is to be loaded entirely from the serialized structure (i.e. is -not already declared in the application). Regular pickle.loads()/dumps() can -be used to fully dump any ``MetaData`` object, typically one which was reflected -from an existing database at some previous point in time. The serializer module -is specifically for the opposite case, where the Table metadata is already present - in memory. + not already declared in the application). Regular pickle.loads()/dumps() can + be used to fully dump any ``MetaData`` object, typically one which was reflected + from an existing database at some previous point in time. The serializer module + is specifically for the opposite case, where the Table metadata is already present + in memory. """ @@ -151,4 +152,4 @@ def loads(data, metadata=None, scoped_session=None, engine=None): unpickler = Deserializer(buf, metadata, scoped_session, engine) return unpickler.load() - \ No newline at end of file + -- cgit v1.2.1