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.
Good day,
When enter user & password for phpMyAdmin no entry appear error (Cannot log in to the MySQL server , mysqli_real_connect(): (HY000/2002): Connection refused) pleases help me.
Regards,
Roaa Abdullah ||IT Department ||Rabdullah(a)ebgh.sa<mailto:Rabdullah@ebgh.sa>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Erfan& Bagedo General Hospital. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.
Hi,
Me and Devan were discussing about the current pr 'gsoc' which I have made
for the modular javascript code but the pr has lots of unused files which I
have created for making sure that existing code is not breaking and
contains lot of commented out code.
So we have decided to create a new branch in main repo of phpMyAdmin and
multiple pr's from gsoc branch with small changes which can be reviewed and
then merged into the newly created branch and we'll then keep merging this
new branch into master after review and testing.
So I am closing this gsoc pr and will make multiple small pr's from this
branch by cherry-picking the commits.
Any suggestions regarding this would be welcome.
Regards
Piyush Vijay
Hello everyone,
I'm going to create preview panels for theme generator. As the colours
would be dynamic it's best use to use javascript to change inline style
tags. I know that we are trying to convert all the already present inline
style tags to css files. But I think for changing colours of panels on
pressing preview buttons, the best way is to use style tags for the
background of panels. Any other idea is highly appreciated.
Regards,
Saksham Gupta
Hi,
I'm having some trouble with the testsuite. The daily builds are not
updating, and it looks like it's because the testsuite for phpMyAdmin
5.0-snapshot is failing (ultimately, MySQL on the build server doesn't
allow the testsuite to authenticate with the stored credentials, but I
think that's secondary to the problem I describe below).
When I run the failing test from the QA branch, it is shown as skipped:
> ./vendor/bin/phpunit -c phpunit.xml.nocoverage test/Environment_test.php
> There was 1 skipped test:
>
> 1) Environment_Test::testMySQL
> Error: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: NO)
However, from master, it fails:
> ./vendor/bin/phpunit -c phpunit.xml.nocoverage test/EnvironmentTest.php
> There was 1 error:
>
> 1) PhpMyAdmin\Tests\EnvironmentTest::testMySQL
> PDOException: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: NO)
I don't see anything obvious that would make these two behave
differently. Do you have any thoughts to help me out?
Isaac
Hello Developers,
I'm currently working on this
<https://github.com/phpmyadmin/phpmyadmin/issues/13155> feature as a part
of my GSoC project. Isaac and I have been trying to think of some
workarounds but your ideas are welcome.
I have currently thought of the following workarounds.
Disable drag drop at the backend, but drag drop handlers in javascript are
written in common,js which has other stuff also, so we can either separate
it in some other file(which I don't think would be a good solution because
it might cause some bugs), or we can find a way to expose the configuration
to javascript(not sure but could lead to security issues) or we can leave
the javascript as it is and disable it only on the server side.(it still
works well, I've tested).
Thanks,
Lakshya arora (nulll-pointer)
