On Wed, 15 May 2019 at 05:12, Lucas Nussbaum wrote:
> udd-schema.sql is generated automatically
Great to hear!
Thanks for the update, Lucas!
--Leandro
Hi,
On 14/05/19 at 19:26 -0300, Leandro Doctors wrote:
> On Tue, 14 May 2019 at 19:01, Mattia Rizzolo wrote:
> > TTBOMK, the schema Is just handled pseudo-manually, so any change would
> > need to be applied directly.
> >
> > I'm not even sure if the schema dump in git is current anymore (being
On Tue, 14 May 2019 at 19:01, Mattia Rizzolo wrote:
> TTBOMK, the schema Is just handled pseudo-manually, so any change would need
> to be applied directly.
>
> I'm not even sure if the schema dump in git is current anymore (being 7
> months old).
Then, probably the best course of action would
On Tue, 14 May 2019, 11:42 pm Leandro Doctors, wrote:
> I'll give it a try and open a MR on salsa.d.o to solve this. (I guess
> that changing the schema itself should be trivial. I will only have to
> think a little bit about the migration process of the current DB.)
>
TTBOMK, the schema Is
On Tue, 14 May 2019 at 06:20, Michael Banck wrote:
> Am Montag, den 13.05.2019, 15:44 -0300 schrieb Leandro Doctors:
Hi, Michael!
Thanks for your detailed answer.
> > Package: qa.debian.org
> > Severity: grave
> > Justification: causes non-serious data loss>
> not sure whether that is
retitle 928942 udd: cannot import current dump due to matview referencing
function without schema
done
Hi,
Am Montag, den 13.05.2019, 15:44 -0300 schrieb Leandro Doctors:
> Package: qa.debian.org
> Severity: grave
> Justification: causes non-serious data loss>
not sure whether that is
6 matches
Mail list logo
