[phpMyAdmin Developers] Add support for CHECK constraints

[Lakshay arora]

Since mysql does not provide an option to edit a check constraint or even
to describe it, I was thinking about making that functionality myself.
Check constraints will be saved in a table named pma_checkConstraints in
phpmyadmin databse, where we will store all the info about ccs. This way,
we can also add an option to edit a cc.
I'll also create a new class CheckConstraint which will handle all the
functionality.
Any suggestions??

On Thu, Jul 5, 2018 at 10:24 PM, Maurício Meneghini Fauth <
mauriciofauth at gmail.com> wrote:

> Hi,
>
> I think it would be better on the server side.
>
> Maurício
>
> On Thu, Jul 5, 2018 at 2:11 AM Lakshay arora <arora.lakshya123 at gmail.com>
> wrote:
>
>> Hello,
>> I've made the ui for adding check constraints. Ive taken reference from
>> qbe.
>> But it generates sql query in javascript in the file
>> db_multi_table_query.js
>> I'm unsure whether I should generate the query on client or server side??
>> Any suggestions??
>>
>> On Wed, Jul 4, 2018 at 2:12 AM, Lakshay arora <arora.lakshya123 at gmail.com
>> > wrote:
>>
>>> Hello,
>>> I'm currently working on this
>>> <https://github.com/phpmyadmin/phpmyadmin/issues/13592>(Add support for
>>> CHECK constraints), as a part of my GSOC project.
>>>
>>> As Isaac has written in his comment, this feature involves three parts.
>>> The order in which I want to work on this is the following -
>>> 1. Implement an interface for interacting with these constraints
>>> 2. Update parser to understand this syntax
>>> 3. Update the export interface to allow including these in an export
>>>
>>> For the first part-
>>> I am thinking of implementing this something like query by example,
>>>   - we show the operator in a select dropdown, and 2 options, to enter
>>> value or another column name
>>> The constraints will be shown like indexes are, in the table structure,
>>> where there will be an option to delete or add new check constraint on the
>>> table.
>>>
>>> For second and third parts-
>>> Not sure yet.
>>>
>>
>> _______________________________________________
>> Developers mailing list
>> Developers at phpmyadmin.net
>> https://lists.phpmyadmin.net/mailman/listinfo/developers
>>
>
> _______________________________________________
> Developers mailing list
> Developers at phpmyadmin.net
> https://lists.phpmyadmin.net/mailman/listinfo/developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.phpmyadmin.net/pipermail/developers/attachments/20180707/add5e1d4/attachment.html>