Message-ID: <a99c5ed6-0e05-2a0c-bef0-4bbb3e04898b@cmatte.me>
Date: Wed, 27 Oct 2021 12:04:02 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.0
Subject: Re: [PATCH] pgarchives: Bugfix: allow message's parentid to be null
Content-Language: en-US
To: pgsql-www@lists.postgresql.org
References: <4280598e-cbe7-c5d3-fbce-fefce11da5f3@cmatte.me>
 <723b45bd-0c14-83eb-1911-b4f481e1b74c@cmatte.me>
 <CABUevEyFpYPEHh0AAyTAsgymRKOOVA1SY_pDHPCbBQQ9BawfTA@mail.gmail.com>
From: =?UTF-8?Q?C=c3=a9lestin_Matte?= <celestin.matte@cmatte.me>
In-Reply-To: 
 <CABUevEyFpYPEHh0AAyTAsgymRKOOVA1SY_pDHPCbBQQ9BawfTA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/a99c5ed6-0e05-2a0c-bef0-4bbb3e04898b%40cmatte.me>
Precedence: bulk

> 
> 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