Hi List,
I've got my SQL parser 100% now given the information that I have.
It's ~10% slower than the speeds I posted before, but I think those are
fast speeds still. Just in case somebody wants to put in a huge chunk of
SQL in one of the SQL input boxes, and they don't really care about my
parser seeing it, I think we should add a checkbox for them to bypass it
if they want to. I see this as being really important if they are using
the SQL upload box to run a really large SQL query, so maybe we even
disable it automatically if they put in a query larger than a certain
size. I'd say possibly all queries larger than 2k should not be parsed, as
the odds say that the query is being pasted in from somewhere else.
The funniest thing that, is I have now found two bugs in the parser
mechanism of MySQL, and submitted bug reports for them. I haven't seen any
reply yet tho.
The main parser function is ready for merging in the source tree, apart
from needing to be re-indented to match the rest of the code in PMA. On
that note, could somebody make some suggestions as to settings for VIM to
indent the sourcecode like we want it.
I'm just tidying up the code of the extractor and the pretty-printer,
and once those are all ready, they will be integrated into the source
tree all at once. The entirety of my code is running ~900 lines at the
moment, so I will put it into a new file, lib/parser.inc.php3.
I've been invited on a short vacation on the 12th and 13th of this month,
so I don't know if I will have the extractor ready for our -rc3 point on
Sunday.
I'll do my best to have it ready by Sunday, but I probably won't manage.
--
Robin Hugh Johnson
E-Mail : robbat2(a)orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
Hi List!
>I've got my SQL parser 100% now given the information
>that I have.
Great :))
>I see this as being really important if they are using
>the SQL upload box to run a really large SQL query, so
>maybe we even disable it automatically if they put in
>a query larger than a certain size.
Right, as we just do something like that to not display
the queries submitted at the top of the page if they are
more than 15 at once.
>The main parser function is ready for merging in the source
>tree, apart from needing to be re-indented to match the rest
>of the code in PMA. On that note, could somebody make some
>suggestions as to settings for VIM to indent the sourcecode
>like we want it.
Yep, as stated in the documentation ;) just have a look at
the "PEAR Coding Standards" page and mainly at this page:
http://pear.php.net/manual/en/standards.php#standards.indenting
Loïc
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif
Let us submit http://www.phpmyadmin.net for FREE on Japanese search engines, German search engines, Hispanic search engines , French search engines , Chinese search engines etc.....!
After reviewing http://www.phpmyadmin.net, we have noticed that your website cannot be found on foreign search engines. Could you please put me in touch with your marketing director or whoever is in charge of web promotion for your website?
As it stands Internet users searching on German search engines, French search engines, Hispanic, Portuguese, Italian, Japanese or Chinese search engines cannot find your website! In fact, it has not been optimized nor listed accordingly ....
We will show you how to reach these multilingual markets without even having to translate your website!
International search engines submission is not about doing business with foreigners in their native language but rather bringing foreigners to your website to do business with you in English!
There are millions of foreigners who speak English but would rather use their native language to conduct a search. From the Japanese Yahoo to the German AltaVista, from the Spanish Lycos to the French Excite, get users to find your website when searching with Your Keywords in Their Mother Tongue.
Let us submit your website on International search engines for FREE! Visit us at http://www.CyberMultilingual.com for full details!
I do believe that a website like yours deserves a better exposure to international markets and this is why I would like to introduce you to our company: CyberDifference Corp. is an international website development agency mainly specialized in multilingual search engines submission in French, German, Spanish, Portuguese, Italian, Japanese, Chinese and Korean.
You may request additional info by email at seo(a)cybermultilingual.com or call my office to schedule a free phone consultation: 1(928) 203 0835...
Test a few markets! What will it be? The German web? The Japanese web? The French web? The choice is yours!! Let's double your Web exposure: reach "the other half of the Internet"! We will perform FREE monthly submissions for your site on foreign search engines....
Regards,
Mathias LEVAREK Ph.D.
seo(a)cybermultilingual.com
___________________________________________________________________
C Y B E R D I F F E R E N C E C O R P.
PO BOX 2735
SEDONA, ARIZONA 86336 USA
TEL:1(928) 203 0835 - FAX: 1(413) 622-3040
http://www.CyberMultilingual.com:
Multilingual search engine submission.
http://www.MetaNovation.com:
Advanced search engine promotions through mirror site marketing
http://www.SearchEngineJungle.com:
Search Engine Promotion Seminars.
This is not a spam: You are receiving this message because " phpmyadmin-devel(a)lists.sourceforge.net " is in our data base from a subscription to one of Cyberdifference Corp.'s international / multilingual e-marketing newsletters. If you want to opt-out and remove your records from our databases please email remove(a)cybermultilingual.com and mention "http://www.phpmyadmin.net" in the subject line. We comply with every removal / opt-out requests.
Hi List!
Rabus wrote:
>I've just merged your patch.
Thanks. I've also put a patch against bug #579017 in
the bug tracker. It would be nice if someone can test
it and submit it into the CVS tree.
Thanks,
Loïc
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif
Marc, did you received my mails? Your server seem
to refuse them all :(
BTW I've put the fix against bug #578404 (js error in
no-frame mode) in the bug tracker. Could you submit it,
please?
Thanks,
Loïc
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif
Hello
I send you this email because there is an error in phpmyadmin when using internet explorer 6. When using it, you get a javascript error on line 62...
Regards
Raf De Leu
Hi,
I suggest a -rc3 on July the 14th, and 2.3.0 on July the 28th.
IMHO the goal is not to fix all bugs. There are some bugs that would
need major
modifications of the code (for example Relation and order by), and I can
live
with them in 2.3.0. It's not time for large modifications of the code.
Marc
>
> > 2. Adding an "PMA_mysqlDie()" inside the wrapper (just like
> > within "PMA_query_as_cu" is also a problem since sometimes
> > we may not want the error to be displayed.
>
> so i'll change the function call so that you can send a
> variable stating
> that you do not want
> the error to displayed and per default display it, ok?
> (if i am using my function anyway i prefer to have the
> function check for
> errors for reasons of lazyiness)
this is done. please try using
PMA_query_as_cu($sql,FALSE)
to not have it die
>
> >
> > For example, just define a "pmadb" that does not exist in the
> > config file and try to do something with phpMyAdmin: you
> > always get a MySQL error message while we should only ignore
> > bookmark/relation... features in this case.
> >
now the relation_inc checks if it can find the pmadb and otherwise will
disable relation features.
--
Mike Beck
mike.beck(a)users.sourceforge.net
Hi Mike!
> 2. Adding an "PMA_mysqlDie()" inside the wrapper (just like
> within "PMA_query_as_cu" is also a problem since sometimes
> we may not want the error to be displayed.
>so i'll change the function call so that you can send a variable
>stating that you do not want the error to displayed and per
>default display it, ok?
Yep, that's fine.
>(if i am using my function anyway i prefer to have the function
>check for errors for reasons of lazyiness)
That's the good practice IMHO but in some case we'd better just
ignore the feature attached to a failing query.
>but rather than a simple ignore i have been thinking of doing
>a debug page which will output all results of the tests, so if
>anybody has problems with the relationfeature he can call this
>page and see where the problem is.
Good idea :)
Loïc
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif
> 2. Adding an "PMA_mysqlDie()" inside the wrapper (just like
> within "PMA_query_as_cu" is also a problem since sometimes
> we may not want the error to be displayed.
so i'll change the function call so that you can send a variable stating
that you do not want
the error to displayed and per default display it, ok?
(if i am using my function anyway i prefer to have the function check for
errors for reasons of lazyiness)
>
> For example, just define a "pmadb" that does not exist in the
> config file and try to do something with phpMyAdmin: you
> always get a MySQL error message while we should only ignore
> bookmark/relation... features in this case.
>
iiks, yup, i just checked if there is anything there. but rather than a
simple ignore i have been thinking of doing a debug page which will output
all results of the tests, so if anybody has problems with the
relationfeature he can call this page and see where the problem is.
--
Mike Beck
mike.beck(a)users.sourceforge.net