Thank you, Egor! It looks like Red Hat released an update to its glibc
libraries yesterday which fix this, so if anybody else is having
problems, they should be able to fix it by updating. :)
Sage
On Thu, 2002-11-07 at 17:46, Egor Egorov wrote:
> Sage,
> Wednesday, November 06, 2002, 3:31
I'm running MySQL 3.23.49 on Red Hat 7.3, with the latest kernel
(2.4.18-17.7.x) installed. It is running in smp mode on a dual P3 1.0
gHz.
MySQL works perfectly fine when connecting from the localhost. However,
I have another machine that needs to connect via ODBC. The ODBC client
can connect, bu
urprise, turns out MySQL behaves not the way I thought it would,
but rather the way you thought it should. Are you perhaps running a
different version? And could you perhaps show us your table structure(s) and
query so that we can find out what's really happening there?
Cheers,
Christian Sage
, of course, whether this is workable. And,
yes, from a design point of view it IS ugly.
cs
> -Ursprüngliche Nachricht-
> Von: Dana Powers [mailto:[EMAIL PROTECTED]]
> Gesendet: Sonntag, 16. September 2001 00:14
> An: Christian Sage
> Cc: [EMAIL PROTECTED]; [EMAIL PROTEC
ffense intended,
as I say, I may be totally off the beam here.
Cheers,
Christian Sage
> -Ursprüngliche Nachricht-
> Von: Dana Powers [mailto:[EMAIL PROTECTED]]
> Gesendet: Samstag, 15. September 2001 23:37
> An: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Betreff: Re: BDB
Only to make sure we don't have any OS-specific I tried your test on my
Win32 installation. Same result:
---< snip
mysql> create table test (seconds bigint not null primary key);
Query OK, 0 rows affected (0.00 sec)
mysql> insert into test values (998556700), (113720), (11);
Query O
your development.
Also, there may be better solutions. If so, the list will probably point
them out to you. ;-)
Cheers,
Christian Sage
-Ursprüngliche Nachricht-
Von: Ville Mattila [mailto:[EMAIL PROTECTED]]
Gesendet: Samstag, 8. September 2001 18:17
An: MySQL-mailinglist
Betreff: SELECT-problem