>>
>
> Were/Are you planning to include a database schema beyond key->value blobs?
>
Agree. The Cyrus key-value store model is very basic. It would be
nice to have a key-structured value model such as redis' one.
2011/10/11 Bron Gondwana :
> Hi,
>
> Is there anyone out there using the SQL backend in production?
>
> Would you be really sad if I redesigned it?
It's OK. We don't use yet the SQL backend but our internal legacy's one.
>
> And if anyone has put together any other backends, I'm interested. I th
On 11.10.2011 00:04, Bron Gondwana wrote:
Hi,
Is there anyone out there using the SQL backend in production?
Would you be really sad if I redesigned it?
Were/Are you planning to include a database schema beyond key->value
blobs?
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab
On Tue, 2011-10-11 at 01:04 +0200, Bron Gondwana wrote:
> Is there anyone out there using the SQL backend in production?
> Would you be really sad if I redesigned it?
> Here's what I'm thinking:
> a) split into per-DB backends, i.e. "sqlite", "mysql", "pgsql".
A unixODBC backend would be very usef
On Oct 10, 2011, at 7:04 PM, Bron Gondwana wrote:
> Hi,
>
> Is there anyone out there using the SQL backend in production?
>
Yes. We use it for the userdeny database.
> Would you be really sad if I redesigned it?
>
Not at all.
Thanks!
Dave
Hi,
Is there anyone out there using the SQL backend in production?
Would you be really sad if I redesigned it?
Here's what I'm thinking:
a) split into per-DB backends, i.e. "sqlite", "mysql", "pgsql".
b) one sqlite file per database (same path as current DBs)
c) one connection per database (b
