Michael Stassen wrote:
Just a quick reply for now . . .
Ummm, if you delete the numbers to the *left* of the decimal point,
2005-01-15 10:15:42.41837 will turn into .41837, which is still not
a valid datetime. You need to delete the numbers to the *right* of the
decimal point (which I
Obviously you can do a join when the names of id columns are different as
well. Look in the doc for that. This has nothing to do with your problem of
finding rows not in another table - it is a basic sql thing.
Stefan
Am Sunday 26 March 2006 00:47 schrieb barney:
Thanks, Stefan,
But that
I've just started trying to use mysql (debian/linux
4.0.24_Debian-10sarge1-log), which I'm finding quite frustrating.
I have a bunch of .csv files to try to import. They all have a first
line containing field names.
When I try load data ...
I get errors no matter what I try
mysql use
Hello
No one at [EMAIL PROTECTED] seemed to know; i am posting here a few days.
A strange case - why would two seemingly identical circumstances yield these
different results?
Machines involved:
Machines A and B - two systems identical in OS versions and MySQL server
installations. A third
Michael Friendly wrote:
I've just started trying to use mysql (debian/linux
4.0.24_Debian-10sarge1-log), which I'm finding quite frustrating.
I have a bunch of .csv files to try to import. They all have a first
line containing field names.
When I try load data ...
I get errors no matter what
select criteria into outfile name of output file
The path for the output file must be writeable by the user underwhich
mysql is running.
--
Curtis Maurand
mailto:[EMAIL PROTECTED]
http://www.maurand.com
On Fri, 24 Mar 2006, Pure Web Solution wrote:
you can manipulate mysqldump using the
In the last episode (Mar 26), Andrew said:
What could ever be the problem with the failing Perl DBI (C-B)
connection, if everything is OK with a C-A connection (with and
without Perl), and, in addition, a command-line C-B connection
works?
The password on B is a new-style password, and perl
David P. Donahue wrote:
/usr/libexec/mysqld: File '/var/log/mysql.01' not found (Errcode: 13)
[ERROR] Could not use /var/log/mysql for loggins (error 13). Turning
logging off for the whole duration of the MySQL server process.
[ERROR] Aborting
If I touch the file, the error is for
In the last episode (Mar 26), Andrew said:
What could ever be the problem with the failing Perl DBI (C-B)
connection, if everything is OK with a C-A connection (with and
without Perl), and, in addition, a command-line C-B connection
works?
The password on B is a new-style password, and perl
rb wrote:
Hi!
Does anyone know the cause of the following error message
Ignoring query to other database
When I log onto the mysql monitor and use any command I get this message.
This is strange because last time I used my copy of mysql it worked just
fine.
I am using MAC OSX and I was
Andrew
Your client application is trying to authenticate with the old mysql
method, you need to update your client script or alternatively reset
password to old version using:
SET PASSWORD FOR 'some_user'@'some_host' = OLD_PASSWORD('newpwd');
Hope this helps
Regards
Jeremy
--
Jeremy
Lola J. Lee Beno wrote:
snip
Here's an example of one of the tables where the date was retained
successfully, with the string to the right of the decimal point being
trimmed:
1Cobweb2005-01-13 15:21:50.654149
2Lace Weight2005-01-13 15:21:50.654149
3Sock2005-01-13
Andrew wrote:
In the last episode (Mar 26), Andrew said:
What could ever be the problem with the failing Perl DBI (C-B)
connection, if everything is OK with a C-A connection (with and
without Perl), and, in addition, a command-line C-B connection
works?
The password on B is a new-style
Hello.
We have a web application for our intranet, which uses MySQL for db
management. The application has a way of logging query errors that are
generated in the system.
We get a mysql error recorded as - Deadlock found when trying to get
lock;
try restarting transaction when
Rithish Saralaya wrote:
snip
in 4.1.xx, you can use the my.cnf option innodb_locks_unsafe_for_binlog to
make InnoDB to use a consistent read in the SELECT tables in CREATE ...
SELECT. Read the caveats about the my.cnf option, though.
Thanks. However, whatever is written in
Shawn Sharp wrote:
I get the following error while trying to create the following database
mysql mysql zm_create.sql.in
ERROR 1044 (42000): Access denied for user ''@'localhost' to database
'mysql'
You are logged into mysql as the anonymous user, ''@'localhost'. By default,
the
Shawn Sharp wrote:
Dilipkumar,
Thanks much for the tipit did the job!
Now we query mysql to see if the new mysql database is seen by mysql and it
still only sees test:
No, you can't see the mysql db, because you don't have permission to access it.
I expect you are still logged in as
As 11 4, 4.1.11 is newer than 4.1.4, so this variable is available to
you.
Gawwddd... I really made an ass of myself that time... :o) Thanks for
pointing it out though.
4.1.11 is almost a year old. Have you read the list of bugs fixed since
then?
This was done as root and shows that TZ works.
dk:/usr/local/mysql # bin/mysql -V
bin/mysql Ver 14.12 Distrib 5.0.18, for pc-linux-gnu (i686) using
readline 5.0
dk:/usr/local/mysql # echo $TZ
dk:/usr/local/mysql # bin/mysqld_safe --user=mysql
[1] 802
dk:/usr/local/mysql # Starting mysqld
19 matches
Mail list logo
