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