Hi,
I just noticed something that is most probably a security bug in QA_4_2
which breaks the regular functioning to phpMyAdmin completely.
Are such bugs to be reported on bug tracker or there is some other place? I
have not published anything about it anywhere yet.
--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/
Hi,
I have an idea to limit the number of bugs in RFE #1518 (Navigate away
patch). That feature is currently applied to all input/textarea elements on
all pages. However, it is not useful on every page/form elements. So, we
can limit this feature to certain pages/forms on which it can be useful by
adding a class "no-navi" (need a suggestion for better class name) to forms
on which we require this feature and listen on only those forms having this
class. Doing this change will not require much time and for a test we can
add this to class to few forms and can extend it later. I can create a PR
to do this.
1) What are your views regarding this idea?
2) On what pages/forms we need this feature? (only few, so that we can test
this feature)
This will certainly not fix the bugs mentioned in tracker but surely can
limit it to certain pages.
--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/
I'm looking at this StackOverflow question [1], and notice strange behavior.
If I insert a row by clicking the Insert tab, I get the expected result
" 1 row inserted. Inserted row id: 11". If I then submit the returned
SQL statement without any modifications, the row is inserted as expected
but the resulting message is "MySQL returned an empty result set (i.e.
zero rows). (Query took 0.0130 seconds.)"
Any thoughts about this?
1 -
https://stackoverflow.com/questions/24135506/how-to-show-inserted-affected-…
Hi,
The phpMyAdmin bot just spammed my email address with 100+ github email
notifications. Is phpMyAdmin bot gone crazy or something new has been added
to it?
--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/
Hi,
While analyzing the current behavior of export feature, few doubts has
arisen in my mind regarding it. In sql_export.png, There are two export
buttons, button 1 & button 2 respectively. When exporting using Button 1
shown in sql_export.png, the resulting sql file had all the rows (20 rows)
present in the table (See QA_4_2_Button_1_export.sql) whereas when Button 2
was used then only the rows (10 rows) displayed in results according to the
LIMIT condition in the query were in the sql file (See
QA_4_2_Button_2_export.sql). Is this the correct behavior or both should
have generated identical sql export file?
SQL query which was used: SELECT * FROM `abcd` WHERE 1 limit 10
--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/
Welcome to phpMyAdmin 4.2.3, a bugfix release. Please note that this
release enforces the minimum PHP (5.3) and MySQL (5.5) versions.
Details will appear on http://phpmyadmin.net. You can also visit
https://sourceforge.net/projects/phpmyadmin/files to download.
The phpMyAdmin team
Hi,
Please see the line 28 of [0] which is the var_dump of
PMA_SQP_analyze(PMA_SQP_parse($create_query)). The 'table_ref' index is an
empty array.
I think it should have name of the table to be created or current one is
correct?
Because in the result there is no index which mention table name separately.
Also, at [0]#L34: 'create_table_fields' index should contain only column
details if I am not wrong. But at [0]#L44, 'latin_general_ci' which is
actually the collation of the table, is appearing in the middle. Is this a
desired behaviour or it is a bug?
Note: The query passed is present in 'unsorted_query' index at [0]#L16.
[0]: http://pastebin.com/YcbuivPB
--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/
Hi,
the value 'pos' attribute as per phpdoc (sqlparser.lib.php, Line 65) is:
@param int $pos Position of an element
So, it should be the index of first character of the element but from [0]
it looks like it is set to index of the last character of element + 1.
Also, for quote_backtick types and few others the value of pos is 0.
What should be the appropriate value for pos?
(Considering 0-based indexing)
1. position of initial character of the element. (I personally prefer this
one).
2. position of last character of the element.
3. position of last character of the element + 1.
Is it used somewhere yet??, because changing its behaviour can cause side
effects.
[0]: http://pastebin.com/EQU3X8H6
--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/