List:General Discussion« Previous MessageNext Message »
From:bali Date:May 29 1999 7:03pm
Subject:prob w/timestamp after upgrading glibc from 2.1.1-5 to higher
View as plain text  
>Description:
	after upgrading glibc (on a debian potato system) to 2.1.1-6,
update table set timest=19990101100101 doesn't work. usually sets the field
to zeroes (Rows matched: 1  Changed: 1  Warnings: 1). I tried to recompile
mysql, even 3.22.22 with libc 2.1.1-6 and 2.1.1-9 (final 2.1 release) but
nothing changed. With quotes around the value it's fine, but we use MyODBC
to connect to the server and it also fails updating any timestamp values.

MyODBC settings are: Don't optimize col width, Allow BIG results, Pad char to full
length. 

Any solutions?

Is it just an incompatible glibc change? 

TIA

---Balint Toth



>MySQL support: none
>Severity:	serious
>Priority:	medium
>Category:	mysql
>Class:		sw-bug
>Release:	mysql-3.22.20a (Source distribution)

>Environment:
	
System: Linux server 2.2.9 #35 SMP Sat May 15 00:33:18 CEST 1999 i686 unknown
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release)
Compilation info: CC='gcc'  CFLAGS='-O2 -fomit-frame-pointer'  CXX='c++'  CXXFLAGS='-O2
-fomit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti'  LDFLAGS=''
Configure command: ./configure  --enable-shared --enable-assembler --enable-shared
--with-mysqld-user=mysql --with-unix-socket-path=/var/lib/mysql/mysql.sock --prefix=/usr
--exec-prefix=/usr --libexecdir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share
--localstatedir=/var/lib/mysql --infodir=/usr/info --includedir=/usr/include
--without-bench --mandir=/usr/man
Perl: This is perl, version 5.004_04 built for i386-linux


Thread
prob w/timestamp after upgrading glibc from 2.1.1-5 to higherbali29 May
  • prob w/timestamp after upgrading glibc from 2.1.1-5 to higherMichael Widenius3 Jun