Hello everyone,
I would like to add this [0] wiki link to the query results chart page. This
link tells what table formats are accepted for query results chart. So if a
user sees that the result cannot be drawn as a chart, he could follow this
link and see how the data needs to be formatted.
I wanted to ask if this is a good idea to link wiki (and especially Devel
category) to PMA. Maybe I should write to the FAQ section in the
documentation everything about accepted formats and then link to
documentation as it is done elsewhere.
[0]
http://wiki.phpmyadmin.net/pma/Devel:Charts#Data_formats_for_query_results_…
Hi,
This is the last week for the Google Summer of Code, and we are
supposed to be documenting our code changes. The coding guidelines on
the phpMyAdmin Wiki say that the comment syntax must be JSDoc
compatible.
As JSDoc is no longer maintained, I downloaded JSDoc-Toolkit, and
tried running it on some of my jQuery and JavaScript code. The
toolkit could correctly parse all the functions written in JavaScript,
but it could not document the jQuery procedural code. I searched on
the net, but could not see any examples of jQuery code being
documented with this toolkit. There are examples of jQuery plugins
and functions being documented with JSDoc-Toolkit, but could not find
anything for simple jQuery scripts.
Has anyone seen JSDoc working with jQuery? (or for that matter, any
other JavaScript library. We could learn from how it was implemented
for them.) I discussed this issue with Ankit today, but even he was
trying to figure out how to do this. If there is no such example
available, how do we proceed for this week, before we submit our code
samples to Google? The comments will be part of my code, whether the
toolkit can parse them or not.
--
Ninad S. Pundalik
hi folks,
I am in a need of using pslib extension for EPS Schema Export. I got the
extension from http://pecl.php.net/package/ps
but I don't know how I will use it in my local wamp ? Also, will that be ok
to use this lib for EPS Schema Export ? I am asking because Users of this
EPS Export will need to download/host this extension ..
--
Muhammad Adnan
Twitter: @hiddenpearls
Failure takes you higher than success ..!
Hi, hopefully one of you can help me figure out a git question I have. I
know the specific revision where a change occurred -- for example
rRELEASE_3_3_4-5777-gd7192b3 (DefaultCharset depreciated), but what I
want to know is what release version that change will affect. Any hints
how I can figure out in which release this will occur?
Thanks,
~isaac
Hi,
During the saving of an inline edit, I'm generating the update query
with JavaScript on the client side, and posting it to tbl_replace.php,
which prepares some variables for sql.php. sql.php then executes the
update query, and generates an output in JSON, which is evaluated by
jQuery at the client side. If the query has been successful, the
values that were in the textarea/input fields, are taken as the new
value for that field and the HTML is updated to that effect.
The above process creates a few problems for me. When the table being
edited has a foreign key or transformed field, the javascript does not
know what is the value to be displayed after a successful edit. For
the foreign keys, I am generating the anchor at the server side in
sql.php and adding it to the JSON output. However, the anchor is not
being generated correctly, as the WHERE clause is missing. After the
query has been executed, sql.php does not know the values of
individual fields, and hence, I cannot generate the WHERE clause
necessary for the anchor.
Similarly, for transformations, I don't have the value of the field,
and hence, I cannot transform the new value to generate the HTML,
which I can add to the JSON output.
In libraries/display_tbl.lib.php, the WHERE clause is generated on the
fly for each field, as '= <field's value>', while the transformation
is done in the function PMA_prepare_row_data().
The solution I have in mind for the transformation problem is to post
an associative array to tbl_replace.php containing the field name and
it's new value, which I'll use after the query has been executed and
generate the HTML with this array. As for the first problem (foreign
key's anchor), I've been stuck at it for some time and can't see a way
out.
Could someone suggest a better solution?
Thanks!
--
Ninad S. Pundalik
