On Fri, Jun 10, 2016 at 2:23 PM, Ken Tanzer wrote:
> On Fri, Jun 10, 2016 at 1:47 PM, Steve Atkins wrote:
>
>>
> You could look at one of the existing SQL parsers implemented in PHP, and
>> use those to parse the constraint to a tree from which you
On Fri, Jun 10, 2016 at 1:54 PM, rob stone wrote:
>
> Hi Ken,
>
> Would this be static or dynamic?
> For example, if you altered a column to become defined as NOT NULL,
> say, when you build the form used to maintain that table you'd like to
> have a "required" attribute
On Fri, Jun 10, 2016 at 1:47 PM, Steve Atkins wrote:
>
> You could name the check constraints, catch the errors and use a
> client-side mapping between constraint name and a friendly error message
> for display in the web interface.
>
> This seems plausible, but not ideal. I
On Fri, 2016-06-10 at 13:01 -0700, Ken Tanzer wrote:
> Hi. I was hoping this list might be able to offer some
> help/advice/suggestions/opinions about feasibility for something I
> want to implement, namely converting Postgres constraints into PHP
> logic. Here's the context and explanation:
>
> On Jun 10, 2016, at 1:01 PM, Ken Tanzer wrote:
>
> Hi. I was hoping this list might be able to offer some
> help/advice/suggestions/opinions about feasibility for something I want to
> implement, namely converting Postgres constraints into PHP logic. Here's the
>
Hi. I was hoping this list might be able to offer some
help/advice/suggestions/opinions about feasibility for something I want to
implement, namely converting Postgres constraints into PHP logic. Here's
the context and explanation:
I work on a PHP web app using Postgres. When possible, we try