Correct and rework requires interface. Remove unused code.

[stub42]

Backwards incompatible changes, so hopefully not too many people are trying to use the current implementation. The old interface was very limited and only useful for simple charms needing a single non-replicated data source. Real systems need replication and multiple data silos for scale out.

[stub42]

This supersedes #3

[stub42]

FWIW, charms using the current interface are not suitable for production deploys as they fail as soon as a second PostgreSQL is added, so no redundancy or simple scale out. It also doesn't support multiple data silos (a charm with multiple pgsql relations), nor sharding (where you have 1..n PostgreSQL services related)

[bcsaller]

This was only ever an example. I suggest we move the repo to one you own,
are you ok with that?

On Mon, Aug 1, 2016 at 2:59 AM stub42 notifications@github.com wrote:

FWIW, charms using the current interface are not suitable for production
deploys as they fail as soon as a second PostgreSQL is added, so no
redundancy or simple scale out. It also doesn't support multiple data silos
(a charm with multiple pgsql relations), nor sharding (where you have 1..n
PostgreSQL services related)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#4 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGVhTSd3XIe4iiiKfaE8mudSSspaiZIks5qbcN_gaJpZM4JBgyh
.

[stub42]

Sure. I'll put it in a new home and update the interfaces registry.