I tried to install drupal (actual stable (7.21)) to mysql. I got
"SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'created' at row 1 "

But when I changed all tiny/small/int to bigint in includes/database/mysql/schema.in it succeded.
(Int wasnt enought)

Comments

vlajos@gmail.com’s picture

It was the installers 3-4. step. After the db credentials setup.

And of course this is mysql. (absoulte default)

vlajos@gmail.com’s picture

Operating system 2013.03.28's debian sid.

$ dpkg -l |grep -i -e php -e mysql
ii  libapache2-mod-php5filter             5.4.4-15                           amd64        server-side, HTML-embedded scripting language (apache 2 filter module)
ii  libdbd-mysql-perl                     4.021-1+b1                         amd64        Perl5 database interface to the MySQL database
ii  libmysqlclient18:amd64                5.5.30+dfsg-1                      amd64        MySQL database client library
ii  libqt4-sql-mysql:amd64                4:4.8.2+dfsg-11                    amd64        Qt 4 MySQL database driver
ii  mysql-client-5.5                      5.5.30+dfsg-1                      amd64        MySQL database client binaries
ii  mysql-common                          5.5.30+dfsg-1                      all          MySQL database common files, e.g. /etc/mysql/my.cnf
ii  mysql-server-5.5                      5.5.30+dfsg-1                      amd64        MySQL database server binaries and system database setup
ii  mysql-server-core-5.5                 5.5.30+dfsg-1                      amd64        MySQL database server binaries
ii  php-apc                               3.1.13-1                           amd64        APC (Alternative PHP Cache) module for PHP 5
ii  php5-cgi                              5.4.4-15                           amd64        server-side, HTML-embedded scripting language (CGI binary)
ii  php5-cli                              5.4.4-15                           amd64        command-line interpreter for the php5 scripting language
ii  php5-common                           5.4.4-15                           amd64        Common files for packages built from the php5 source
ii  php5-gd                               5.4.4-15                           amd64        GD module for php5
ii  php5-mysql                            5.4.4-15                           amd64        MySQL module for php5
Ciprian Oancia’s picture

How did I got it fixed.
1. I did enabled mysql.log
2. At each atempt to install Drupal I saw that query stops at user insert (due to created collumn)
3. Checked again phpinfo(); related to the time issue and I saw that _SERVER["REQUEST_TIME"] is in microseconds instead of seconds. (php 5.4.4-14)
4. I did a quick and dirty fix (someone please suggest a better way) by adding in php.ini auto_prepend_file=/somepath/prepend.php and inside that file:

$_SERVER['REQUEST_TIME_FLOAT'] = time();
$_SERVER['REQUEST_TIME'] = time();

5. restarted apache :)
hope this helps you :)

bailey86’s picture

This looks like it could be related to a bug in the Debian package libapache2-mod-php5filter. I've reported it here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709023

My fix was to install the package libapache2-mod-php5 which then replaced libapache2-mod-php5filter.

In fact the package libapache2-mod-php5 should be used in preference to libapache2-mod-php5filter as on the package page for libapache2-mod-php5filter it even says 'Unless you specifically need filter-module support, you most likely should instead install libapache2-mod-php5.'

This has also been reported as a bug - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709027

It could also be related to https://bugs.php.net/bug.php?id=62507

Version: 7.21 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.