Nestor:
You might not have entered the SQL FLUSH PRIVILEGES;
command after you changed the password. Without it, the old
data can remain in effect.
Cheers,
Kent Hoover
-
Before posting, please check:
http://www.mysql.com
On Wed, 11 Sep 2002, Jeremy Zawodny ([EMAIL PROTECTED]) wrote:
On Wed, Sep 11, 2002 at 02:55:01PM -0400, Kent Hoover wrote:
Version: MySQL.3.22.32-log
Does this problem ring a bell with anyone?
I'm seeing two undesired behaviors, both, *I think*
seem to be because I'm
with the same password.
Please, someone, tell me that these 2 problems are both
load related, were found and corrected by a later release
than the one I have.
Thanks,
Kent Hoover
-
Before posting, please check:
http
I would use this query:
SELECT DISTINCT SUBSTRING(email,LOCATE('@', email) ) FROM AddressList ;
Cheers,
Kent
sql, query, y'hear
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
This works for me:
mv /mysql/log /mysql/Oldlog
mysqladmin flush-logs
MySQL follows the oldlog, keeps writing to it until the flush, when it
closes its Oldlog,
and open/create-s its logfile.
Cheers,
Kent
-
Before
I believe the answer will be for you to create a single index on *just*
the cust column. (I assume that a specific cust id occurs only once or a
few times in the
whole table.) This will allow MySQL to use that index to find the small
set of records (quickly) where cust=1,
then to screen the email
Kevin:
A database is, in some sense, a container for your tables. It sounds
like you want
to compose a new container. Thus,
To list your databases (containers):
mysql show databases;
... it seems that the list should contain your dbb and mysql, probably
also test.
To create a new database
Doc:
Try this...
SELECT C.domain, email, telephone, count(*)
FROM Customers AS C LEFT JOIN
Orders AS O ON O.domain=C.domain
GROUP BY C.domain, email, telephone ;
Cheers,
Kent
[fodder=SQL]
-
Before
Read all about Join in the manual -- it includes hints like this query:
SELECT DISTINCT(PersonID) FROM PersonProject AS P1
LEFT JOIN PersonProject AS P2 ON P2.PersonID=P1.PersonID AND
P2.ProjectID=2
WHERE P2.PersonID IS NULL;
Cheers,
Kent
,
Kent Hoover
filter wants me to type 'database' here
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL
You didn't show the code where the mysql_query() is done.
Further, you have RAND as r coded in your select statement,
not RAND( ) as r. Is this live code?
Cheers,
Kent
(filter feeder: database)
-
Before posting, please
The excess space could've come from the very long column name
of the
first field.
Shrink that with an alias:
select if(substring) AS shortname, sec_to_time( ) AS
session ...
Cheers,
Kent Hoover
filter fodder:database,sql
The excess space could've come from the very long column name
of the first field.
Shrink that with an alias:
select if(substring) AS shortname, sec_to_time( ) AS
session ...
Cheers,
Kent Hoover
filter fodder:database,sql
The GET_LOCK() and RELEASE_LOCK() functions might help you,
if
you need this feature enough to build it yourself.
Cheers,
Kent Hoover
Feed the filter: database, query
-
Before posting, please check:
http://www.mysql.com
Does the mysql user have write-permission in the directory where core
would be
written?
Cheers,
Kent
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the
You can update the "first" row by adding LIMIT 1 to your update query.
If the rows are identical, "first" vs. "third" doesn't matter. If it
does matter,
you should probably add a unique, tiebreaking field (sequence or
DateTime, if
you can assure there will never be 2 identical records inserted
I would try running multiple MySQL servers on your backup host machine,
where
each one is a slave to its own respective master DB. I think that keeps
maintenance
of replication/recovery/restore scenarios much cleaner. If your Master
DB A
breaks, what you have to do to recover it from Slave A is
Your table bb is not indexed in a way that helps this query. Creating an
index on min_number may help somewhat.
If your intervals DON'T overlap each other, there's probably a much
better
algorithm for you to use than an SQL join. (e.g., select each number
from aa
in sequence, form a query for
Tried /etc/my.cnf in place of /etc/mysql/my.cnf ?
Cheers,
Kent
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this
Sorry. Sent the last message before I was done
If you have a stray $DATADIR/my.cnf or a $HOME/.my.cnf, their
contents will override what you have set in /etc/my.cnf.
Cheers,
Kent
-
Before posting, please check:
Joel:
I'll take another shot. Do you have spaces in your command? Remove
them.
Change : socket = /var/run/mysqld/mysqld.sock
To: socket=/var/run/mysqld/mysqld.sock
Cheers,
Kent
-
Before posting, please
I see in your 'Explain's, the 2 queries use different indexes, the fast
one uses soc_date_idx, and the slower one uses q_idx. The trick,
perhaps is to force
soc_date_idx to be used in the 2nd case. (Adding ORDER BY soc_date might
do it, 'soc_date=X and (queue_id=Y and server_id=Z) ) might do
You could very well shorten the overall elapsed time if you can
configure your
script into 2 (or more) scripts, each doing 1/2 of your updates, and run
them
in parallel.
Cheers,
Kent
-
Before posting, please check:
$ myisamchk --set-autoincrement-value=1 YourTable.MYI
would reset the number to 1 for you. If you do not remove existing
records from
your table, your MySQL could generate errors as the new value collides
with
an existing record.
Cheers,
Kent
That log rotation script smells like the culprit to me. Exactly what is
it doing?
If it is clipping the file in a way that doesn't let MySQL reset the
file pointer
when you do the flush logs command, you could be max-ing the file out
to its ulimit.
Cheers,
Kent
You can create a "MERGE TABLE" (read all about it in the manual)...
CREATE MERGE TABLE everything ( animalname varchar(25)) TYPE=MERGE
UNION=(table_1,table_2);
Thereafter, you can select * from everything;
Cheers,
K
Outside of MySQL, use a native OS command to rename or remove the
directory named '#Muffin' . If you rename it 'foobar', you should be
able to DROP it with
MySQL.
Cheers,
Kent Hoover
-
Before posting, please check:
http
solution is to not connect via 'localhost', but via your
server's IP address,
for which port 3400 should work.
Cheers,
Kent Hoover
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http
28 matches
Mail list logo
