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.
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@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 -
- Implement an interface for interacting with these constraints
- Update parser to understand this syntax
- 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.
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@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@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 -
- Implement an interface for interacting with these constraints
- Update parser to understand this syntax
- 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@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
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@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@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@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 -
- Implement an interface for interacting with these constraints
- Update parser to understand this syntax
- 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@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Hi developers,
On Sat, Jul 7, 2018 at 3:42 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
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??
I'm uncertain about this feature. On one hand, it seems like an area where we could provide some extra functionality that MySQL doesn't — similar to how we supported relations between tables before InnoDB was so popular. On the other hand, it's not something that's been requested much, isn't expected since it's outside the scope of MySQL's features, and is something that I imagine MySQL will eventually support anyway. Having it in place would only benefit users when using phpMyAdmin directly rather than using any application.
I have a slight inclination to say no to this idea, but I certainly could be swayed another way.
Isaac
I need some help with this. To extend mysql feature, we have to use configuration storage(phpmyadmin database) and it is not set, then I'll have to disable this feature completely(like it doesn't exist). we don't use configuration storage and use only the features provided by mysql. Any suggestions.
On Wed, Jul 11, 2018 at 8:29 AM, Isaac Bennetch bennetch@gmail.com wrote:
Hi developers,
On Sat, Jul 7, 2018 at 3:42 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
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??
I'm uncertain about this feature. On one hand, it seems like an area where we could provide some extra functionality that MySQL doesn't — similar to how we supported relations between tables before InnoDB was so popular. On the other hand, it's not something that's been requested much, isn't expected since it's outside the scope of MySQL's features, and is something that I imagine MySQL will eventually support anyway. Having it in place would only benefit users when using phpMyAdmin directly rather than using any application.
I have a slight inclination to say no to this idea, but I certainly could be swayed another way.
Isaac
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
On Jul 13, 2018, at 4:50 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
I need some help with this. To extend mysql feature, we have to use configuration storage(phpmyadmin database) and it is not set, then I'll have to disable this feature completely(like it doesn't exist). we don't use configuration storage and use only the features provided by mysql. Any suggestions.
That's correct. You may be able to use one of the existing tables or make a new one, but either way if the table doesn't exist, if the configuration storage database doesn't, or if they aren't configured you'll need to just disable the feature.
A good example of how that is handled already is with the internal relations feature that works similar to InnoDB relations.
You've got the right idea, though. If the user doesn't have the proper table structure or has disabled the feature in config.inc.php then we should just disable the enhancement entirely.
Does that help?
On Wed, Jul 11, 2018 at 8:29 AM, Isaac Bennetch bennetch@gmail.com wrote: Hi developers,
On Sat, Jul 7, 2018 at 3:42 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
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??
I'm uncertain about this feature. On one hand, it seems like an area where we could provide some extra functionality that MySQL doesn't — similar to how we supported relations between tables before InnoDB was so popular. On the other hand, it's not something that's been requested much, isn't expected since it's outside the scope of MySQL's features, and is something that I imagine MySQL will eventually support anyway. Having it in place would only benefit users when using phpMyAdmin directly rather than using any application.
I have a slight inclination to say no to this idea, but I certainly could be swayed another way.
Isaac
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Yes, Thank you
On Fri, Jul 13, 2018 at 8:13 PM, Isaac Bennetch bennetch@gmail.com wrote:
On Jul 13, 2018, at 4:50 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
I need some help with this. To extend mysql feature, we have to use configuration storage(phpmyadmin database) and it is not set, then I'll have to disable this feature completely(like it doesn't exist). we don't use configuration storage and use only the features provided by mysql. Any suggestions.
That's correct. You may be able to use one of the existing tables or make a new one, but either way if the table doesn't exist, if the configuration storage database doesn't, or if they aren't configured you'll need to just disable the feature.
A good example of how that is handled already is with the internal relations feature that works similar to InnoDB relations.
You've got the right idea, though. If the user doesn't have the proper table structure or has disabled the feature in config.inc.php then we should just disable the enhancement entirely.
Does that help?
On Wed, Jul 11, 2018 at 8:29 AM, Isaac Bennetch bennetch@gmail.com wrote:
Hi developers,
On Sat, Jul 7, 2018 at 3:42 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
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??
I'm uncertain about this feature. On one hand, it seems like an area where we could provide some extra functionality that MySQL doesn't — similar to how we supported relations between tables before InnoDB was so popular. On the other hand, it's not something that's been requested much, isn't expected since it's outside the scope of MySQL's features, and is something that I imagine MySQL will eventually support anyway. Having it in place would only benefit users when using phpMyAdmin directly rather than using any application.
I have a slight inclination to say no to this idea, but I certainly could be swayed another way.
Isaac
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
I'm working on the parser. I'm seeing the code for the first time. Can someone give me a head start.
On Sat, Jul 14, 2018 at 10:37 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
Yes, Thank you
On Fri, Jul 13, 2018 at 8:13 PM, Isaac Bennetch bennetch@gmail.com wrote:
On Jul 13, 2018, at 4:50 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
I need some help with this. To extend mysql feature, we have to use configuration storage(phpmyadmin database) and it is not set, then I'll have to disable this feature completely(like it doesn't exist). we don't use configuration storage and use only the features provided by mysql. Any suggestions.
That's correct. You may be able to use one of the existing tables or make a new one, but either way if the table doesn't exist, if the configuration storage database doesn't, or if they aren't configured you'll need to just disable the feature.
A good example of how that is handled already is with the internal relations feature that works similar to InnoDB relations.
You've got the right idea, though. If the user doesn't have the proper table structure or has disabled the feature in config.inc.php then we should just disable the enhancement entirely.
Does that help?
On Wed, Jul 11, 2018 at 8:29 AM, Isaac Bennetch bennetch@gmail.com wrote:
Hi developers,
On Sat, Jul 7, 2018 at 3:42 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
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??
I'm uncertain about this feature. On one hand, it seems like an area where we could provide some extra functionality that MySQL doesn't — similar to how we supported relations between tables before InnoDB was so popular. On the other hand, it's not something that's been requested much, isn't expected since it's outside the scope of MySQL's features, and is something that I imagine MySQL will eventually support anyway. Having it in place would only benefit users when using phpMyAdmin directly rather than using any application.
I have a slight inclination to say no to this idea, but I certainly could be swayed another way.
Isaac
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Hi, I'm working on exporting of check constraints. The problem is- We can't access the definition of a constraint in mariadb. And we need the definition of a constraint to save it in the sql dump file, Though I'm saving the constraint in the configuration storage, if storage is not configured, check constraints can't be dumped.
On Sun, Jul 15, 2018 at 1:40 PM, Lakshay arora arora.lakshya123@gmail.com wrote:
I'm working on the parser. I'm seeing the code for the first time. Can someone give me a head start.
On Sat, Jul 14, 2018 at 10:37 AM, Lakshay arora < arora.lakshya123@gmail.com> wrote:
Yes, Thank you
On Fri, Jul 13, 2018 at 8:13 PM, Isaac Bennetch bennetch@gmail.com wrote:
On Jul 13, 2018, at 4:50 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
I need some help with this. To extend mysql feature, we have to use configuration storage(phpmyadmin database) and it is not set, then I'll have to disable this feature completely(like it doesn't exist). we don't use configuration storage and use only the features provided by mysql. Any suggestions.
That's correct. You may be able to use one of the existing tables or make a new one, but either way if the table doesn't exist, if the configuration storage database doesn't, or if they aren't configured you'll need to just disable the feature.
A good example of how that is handled already is with the internal relations feature that works similar to InnoDB relations.
You've got the right idea, though. If the user doesn't have the proper table structure or has disabled the feature in config.inc.php then we should just disable the enhancement entirely.
Does that help?
On Wed, Jul 11, 2018 at 8:29 AM, Isaac Bennetch bennetch@gmail.com wrote:
Hi developers,
On Sat, Jul 7, 2018 at 3:42 AM, Lakshay arora arora.lakshya123@gmail.com wrote:
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??
I'm uncertain about this feature. On one hand, it seems like an area where we could provide some extra functionality that MySQL doesn't — similar to how we supported relations between tables before InnoDB was so popular. On the other hand, it's not something that's been requested much, isn't expected since it's outside the scope of MySQL's features, and is something that I imagine MySQL will eventually support anyway. Having it in place would only benefit users when using phpMyAdmin directly rather than using any application.
I have a slight inclination to say no to this idea, but I certainly could be swayed another way.
Isaac
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
Developers mailing list Developers@phpmyadmin.net https://lists.phpmyadmin.net/mailman/listinfo/developers
-
Isaac Bennetch -
Lakshay arora -
Maurício Meneghini Fauth