Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null

> 
> That said, I think the correct solutoin is still, as I mentioned in one of the other threads, to completely move
everythinginto the initial migration, instead of doing a piecemeal hack that's going to result in a lot of small
migrationsfor no real reason. We should  just accept that the existing one is broken and replace it.
 

Can everything be moved to django's model though? The schema.sql file defines several other components (indexes, text
searchconfigurations, text search dictionaries, functions, triggers) and I'm not sure django is able to handle all of
thatby itself. Is it? Or do you only want to move tables?
 

Cheers,
-- 
Célestin Matte