#4344 Weird values on table overview

4.1.12 (1)

Hi there!

Table overview is behaving bizarre since we were forced to update to MariaDB on Synology. Data werten't lost, but the table overview shows weird values. These values aren't shown anymore once you open an insert. To understand, check the both files attached. Overview shows the weird value, and the second one shows the insert itself once openend, where the values are correct.

I'm running 4.1.12 and server is 5.5.34-MariaDB - Source distribution

2 Attachments


  • Marc Delisle

    Marc Delisle - 2014-04-04

    Please attach a small export of your table's structure and sample data.

  • Psychokiller1888

    Thank you for taking time looking at my problem. Attached the export of one of the table in question

  • Marc Delisle

    Marc Delisle - 2014-04-05

    Cannot reproduce your problem with phpMyAdmin 4.1.12 and 5.5.36-MariaDB (from mariadb-5.5.36-linux-i686.tar.gz).

    Possible causes:
    - you are not using the mysqli PHP extension
    - you have a mismatch between your MySQL client library and your server

    I think you are seeing hex values for this column, because phpMyAdmin thinks that it is binary (due to the causes above). When browsing, open Options and untick "Show binary contents as HEX".

  • Marc Delisle

    Marc Delisle - 2014-04-05
    • status: open --> pending
    • assigned_to: Marc Delisle
  • Psychokiller1888

    Doo, it's fixed... Thank you for your help! I fixed it by settings the extension used to mysqli in my config.inc.php.

    As a review, might be usefull to you:

    • My config.inc.php was setting 'mysql' as used extension
    • Unticking Show binary content did not change anything
    • Settings $cfg['Server'][$i]['extension'] to 'mysqli' solved to problem

    It now shows correct values in both table overview and row edition.

    I consider my problem as fixed and thank you for your help. I let to you the consideration if it's normal that values are not shown same way in overview and edition when using mysql extension (which I know, shouldn't be used anymore, but still)


    Last edit: Psychokiller1888 2014-04-08
  • Marc Delisle

    Marc Delisle - 2014-04-08

    Thanks for the feedback. In the upcoming version 4.2, the $cfg['Server'][$i]['extension'] directive is gone. The mysqli extension is tried first, then the mysql extension (but a clear warning is displayed in this case).

  • Marc Delisle

    Marc Delisle - 2014-04-08
    • status: pending --> invalid

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks