Re: Contenttype Generation Inconsistency During Serialization

On Wed, Feb 11, 2009 at 4:59 PM, jameslon...@gmail.com < jameslon...@gmail.com> wrote: > > This is a great solution; when I wrote this post I was sure no one had > really run into the problem. I will use this for serializing my DB in > the future. Though, the last paragraph of your reply states

Re: Contenttype Generation Inconsistency During Serialization

On Thu, Feb 12, 2009 at 4:48 AM, jameslon...@gmail.com wrote: > > There is a small road block that makes contenttype a little dangerous > to use during application development. Especially in regards to > serializing your data to different databases. During syncdb the >

Re: Contenttype Generation Inconsistency During Serialization

This is a great solution; when I wrote this post I was sure no one had really run into the problem. I will use this for serializing my DB in the future. Though, the last paragraph of your reply states that content type doesn't define app_label and model as unique. I believe that this is true now,

Re: Contenttype Generation Inconsistency During Serialization

On Wed, Feb 11, 2009 at 1:48 PM, jameslon...@gmail.com < jameslon...@gmail.com> wrote: > > There is a small road block that makes contenttype a little dangerous > to use during application development. Especially in regards to > serializing your data to different databases. During syncdb the >

Contenttype Generation Inconsistency During Serialization

There is a small road block that makes contenttype a little dangerous to use during application development. Especially in regards to serializing your data to different databases. During syncdb the contenttypes are generated in a way that makes regeneration at a later date inconsistent with the