moger

hello.. my name moger..

i new in here..

 

how if we learning about bug in php n mysql in here forum..??

i'm not found about bug php & mysql in this forum.!! ------>> may i dont know how to use search fasility in this forum

 

if u wont.. we can start on bug php & mysql maybe..

 

regards

 

if u have a problem in your mysql database u can search about mysql bug on this url

http://bugs.mysql.com/search.php

 

regards

 

Since I'm using PHP 4.2.3 phpMyAdmin (https://www.phpmyadmin.net/) does

not work properly anymore. To me it seems as if string routines would be

broken. As an example I have two errormessages generated from

phpMyAdmin:

 

Creating a simple table with ID as auto_increment:

 

--

CREATE TABLE `atest` (

 

`ID` INT NULL _INCREMENT,

PRIMARY KEY ( `ID` )

)

 

MySQL meldet:

 

You have an error in your SQL syntax near '_INCREMENT, PRIMARY KEY

(`ID`))' at line 1

--

 

It seems as if this PHP version would kill the "auto" in front of

"_increment". Of course, then MySQL produces an error.

 

Second example: If I change a value (DATE), I get the following error:

 

--

UPDATE `termine` SET `datum` = '-09-23' WHERE `ID` = \'42\' LIMIT 1;

 

MySQL meldet:

 

You have an error in your SQL syntax near '\'42\' LIMIT 1' at line 1

--

 

There is one ' too much (changing MagicQuotes did not help anything)

 

I do not thing that this is a problem of phpMyAdmin because I just

recompiled PHP 4.2.2 with exactly the same configure options on the same

system (2 days difference, so no new libraries etc) and everything works

just perfect.

 

My confiugure Line:

--

'./configure' '--prefix=/usr/share' '--datadir=/usr/share/php'

'--bindir=/usr/bin' '--libdir=/usr/share' '--includedir=/usr/include'

'--with-config-file-path=/etc/httpd' '--with-exec-dir=/usr/lib/php/bin'

'--disable-debug' '--enable-bcmath' '--enable-calendar' '--enable-ctype'

'--enable-dbase' '--enable-discard-path' '--enable-exif'

'--enable-filepro' '--enable-force-cgi-redirect' '--enable-ftp'

'--enable-gd-imgstrttf' '--enable-gd-native-ttf'

'--enable-inline-optimization' '--enable-magic-quotes'

'--enable-mbstr-enc-trans' '--enable-mbstring' '--enable-memory-limit'

'--enable-shmop' '--enable-sigchild' '--enable-sysvsem'

'--enable-sysvshm' '--enable-track-vars' '--enable-versioning'

'--enable-wddx' '--enable-yp' '--with-bz2' '--with-ftp' '--with-gdbm'

'--with-gettext' '--with-gmp' '--with-imap=yes'

'--with-jpeg-dir=/usr/lib' '--with-ldap=yes' '--with-mcal=/usr'

'--with-mcrypt' '--with-mysql=/usr' '--with-ndbm' '--with-pgsql=/usr'

'--with-snmp' '--with-t1lib' '--with-ttf' '--with-freetype-dir=yes'

'--with-zlib=yes' '--with-openssl' '--with-curl' '--with-imap-ssl'

'--with-gd=yes' '--with-mm' '--with-apxs=/usr/sbin/apxs' '--with-ming'

'--with-mhash' '--with-pdflib' '--with-png-dir=/usr/lib'

'--with-tiffs-dir=/usr/lib' '--with-iodbc'

--

I do not include a backtrace because PHP does not crash at all. The

system continues to run, the page gets finished and I can continue to

work with PHP.