Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null - Mailing list pgsql-www

From Célestin Matte
Subject Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null
Date
Msg-id a99c5ed6-0e05-2a0c-bef0-4bbb3e04898b@cmatte.me
Whole thread Raw
In response to Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null  (Magnus Hagander <magnus@hagander.net>)
List pgsql-www
> 
> 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



pgsql-www by date:

Previous
From: Célestin Matte
Date:
Subject: Re: [PATCH] pgweb: Add ARCHIVES_FRONT_ADDRESS to allow configuration of archives
Next
From: Magnus Hagander
Date:
Subject: Re: [PATCH] pgarchives: Allow use of IP ranges for SEARCH_CLIENTS