Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Standing question when people have problems with MySQL.

    • Depends on which system we're on, which is one of our main problems.

      MySQL installs with strict mode OFF by default on Linux (at least on the Fedora versions I've seen). The GUI installer on Windows, meanwhile, gives you a checkbox with strict mode enabled by default, which is a good idea in itself, but is a real problem when the default MySQL installation elsewhere is completely different.

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • that's a nightmare... and another reason not to use the database in question (as if there weren't already enough reasons).

    Actually we're using lowercase table and column names and uppercase keywords for ages now which makes the statements very good to read in my opinion.

    This issue would be even more disgusting for us if we had to work with alien databases.
    At least good to know what to take care of and to avoid... just in case... you never know.

  • The reason that database and table names are case-aware in mysql is because they're simply files and directories, and mysql punts to the underlying OS to handle it. Thus, on Windows, they're not case sensitive and on *nix they are. (BTW, I'm not defending it, I'm just pointing out why.)
    --
    (darren)
    • I know that's true for MyISAM tables, but not all storage engines store each table in individual files. Is this true for them?

      • The Views table has ENGINE=InnoDB, and the primary key is ViewID:

        mysql> select count(ViewID) from Views\G
        *************************** 1. row ***************************
        count(ViewID): 0
        1 row in set (0.00 sec)

        mysql> select count(VIEWID) from Views\G
        *************************** 1. row ***************************
        count(VIEWID): 0
        1 row in set (0.00 sec)

        mysql> select count(ViewID) from VIEWS\G
        ERROR 1146 (42S02): Table 'scimitar.VIEWS' doesn't exist

        So InnoDB behaves the same way as MyISAM on Linux. I don't

        --
        (darren)