I'd very much be in favor of this. Constraints on data should indeed be
enforced by the database and/or backend, and not solely by which
front-end you use.
I'm rolling out our authoritative side of things right now, and it's
going to be a pain to check each GUI to make sure it behaves properl
On Thu, Jan 31, 2013 at 08:20:24PM +0100, Jan-Piet Mens wrote:
> > On long, solitary drives I get crazy ideas, and at a beastly hour this
> > morning, it happened again:
>
> FWIW, I'm taking this to [1], where I'm showing some examples of what is
> possible, even though this is probably less than
> On long, solitary drives I get crazy ideas, and at a beastly hour this
> morning, it happened again:
FWIW, I'm taking this to [1], where I'm showing some examples of what is
possible, even though this is probably less than a proof of concept. ;-)
-JP
[1] http://jpmens.net/2013/01/31/co
Thomas,
> At least in my usecase, I'd prefer to place the check logic in to the
> system that fills the pdns database.
> I also think that it is easier to write the check logic with a
> language like Python or Java than with the MySQL Procedure Language.
Absolutely right on both accounts, and if
Hi Jan-Piet,
thanks for sharing your ideas.
At least in my usecase, I'd prefer to place the check logic in to the
system that fills the pdns database.
This, of course, has the shortcoming that the database can be in an
inconsistent state.
But, for example, rectify zone is run when all chan
On long, solitary drives I get crazy ideas, and at a beastly hour this
morning, it happened again:
It ought to be possible (famous last words) to create a set of MySQL
triggers and a couple of User Defined Functions (UDF) which ensure that
data entered into PowerDNS' MysQL database tables (in part
