Dne 01. 02. 23 v 13:56 Milan Crha napsal(a):
Hi,
this is a query for an opinion and a best-practice experience for a
case when a package needs to change its internal database format
between versions, in an environment, which does not allow real
That being said, any such change
On Wed, 2023-02-01 at 10:12 -0800, Kevin Fenzi wrote:
> Is there any way to pull the functionaly into the process itself?
> ie, the first time it's called, it converts the db?
Hi,
the idea is to not depend on the libdb at all, neither in the build
time. I reworked the proposed change to
On Wed, Feb 01, 2023 at 01:56:20PM +0100, Milan Crha wrote:
> Hi,
> this is a query for an opinion and a best-practice experience for a
> case when a package needs to change its internal database format
> between versions, in an environment, which does not allow real
> migration, aka the app
On Wed, 2023-02-01 at 14:15 +0100, Alexander Sosedkin wrote:
> cyrus-sasl ships a migration tool for some transition period
> and suggests the user to manually invoke it:
Hi,
aha, I see, that's much saner idea than what I came up with.
I'll try to cook something similar, making the
On Wed, Feb 1, 2023 at 1:57 PM Milan Crha wrote:
> this is a query for an opinion and a best-practice experience for a
> case when a package needs to change its internal database format
> between versions, in an environment, which does not allow real
> migration, aka the app cannot read both
Hi,
this is a query for an opinion and a best-practice experience for a
case when a package needs to change its internal database format
between versions, in an environment, which does not allow real
migration, aka the app cannot read both formats, it can use one or the
other.
To be
