Re: Implementing SQL ASSERTION

> On 3 May 2015, at 02:42, David Fetter <david@fetter.org> wrote:
>
> On Sat, May 02, 2015 at 10:42:24PM +0100, Joe Wildish wrote:
>>
>> I may start writing up on a blog of where I get to, and then post further to this list, if there is interest.
>
> I suspect that you would get a lot further with a PoC patch including
> the needed documentation.  Remember to include how this would work at
> all the transaction isolation levels and combinations of same that we
> support.  Recall also to include the lock strength needed.  Just about
> anything can be done with a database-wide lock :)

Thanks David. I’m obviously new here so I not that familiar with how one starts contributing.

Once I get to a decent level with the EM4 PoC I will post the details to this list.  The general idea is that upon
assertioncreation, the expression is analysed to determine when it needs to be validated — corresponding internal
"afterstatement” triggers are then created.  There will definitely need to be some serialisation take place on the
basisof when an assertion has been validated, but I’ve not got that far yet.  I’ll be sure to include the details when
Ipost though. 

Regards.
-Joe