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

From: Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
To: pgsql-www(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null
Date: 2021-10-27 10:04:02
Message-ID: a99c5ed6-0e05-2a0c-bef0-4bbb3e04898b@cmatte.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

>
> That said, I think the correct solutoin is still, as I mentioned in one of the other threads, to completely move everything into the initial migration, instead of doing a piecemeal hack that's going to result in a lot of small migrations for 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 search configurations, text search dictionaries, functions, triggers) and I'm not sure django is able to handle all of that by itself. Is it? Or do you only want to move tables?

Cheers,
--
Célestin Matte

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2021-10-27 13:42:00 Re: [PATCH] pgarchives: Allow use of IP ranges for SEARCH_CLIENTS
Previous Message Célestin Matte 2021-10-27 09:58:16 Re: [PATCH] pgweb: Add ARCHIVES_FRONT_ADDRESS to allow configuration of archives