> On Jun 20, 2015, at 10:40 AM, (by way of [email protected]) > <[email protected]> wrote: > > I read about the Serializer Extension and ask myself if it is a good > solution for my problem.
Haven't even read the rest of your email yet, and the answer is no. The serializer works really badly. > > Currently I am using PostgreSQL under my sqlalchemy. There is no way > to make PostgreSQL database "portable" because the database is not > represented as one file I could just copy to another machine. Yes there is. Use pg_dump. > > So when I want to use my application "portable" I think it would be a > good workaround to create a dump-file of the database when the > application is closed and restore it when it is started. > So application > doesn't have to think about on which machine it is running. > > I could access PostgreSQL directly on commandline but it is not > platformindependent. I want to do it with the sqlalchemy-way. Ok to dump the schema you'd use a MetaData object and you'd pickle it. Serializer extension has nothing to do with that. > > Would the Serializer Extension be a good solution for that? The serializer docs state that it is not, read the second bulletpoint near the top. > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
