this is an absolute newbie question - but when i try to run mysqldump with a cron
(like with a shell script) i can't because mysqldump utility stops to ask for a
password. how can I either embed the password or set up mysqldump to not ask for one
if, for instance, root is running the shell
I want to write an efficient query that will delete all records from one
table when they show up in another table (pending shipments -- shipped
shipments). I can't do it with this:
mysql DELETE from pending_2 WHERE pending_2.ordno = ordersearch_2.ordno;
because you can only refer to columns
I'm looking for a new commerce package, something run of a MySQL database.
it's gotta have bulletproof (well, as close as you can get) session
management. I wonder what others on the list are using and like? input is
appreciated!
thanks!
excuse me if this is too newbie...but I need to perform a duplicate
delete on my database using the e-mail address as the key. I understnad
how to use COUNT and DISTINCT together...
select count(DISTINCT email) FROM table;
but I can't seem to find any info on how to perform the actual
I want to leave one record behind, but delete all other records that
have the same e-mail address. Is there a standard query for this or do
I need to write a script that will do it?
THanks,
Rory
On Thu, 30 Aug 2001 22:35:48 -0500, Rory O'Connor [EMAIL PROTECTED]
wrote:
Do you want to delete
I'm a bit of a mysql newbie...excuse if this is rudimentary.
I imported about 5000 records and realized that the index is a bit scewy
since i deleted alot of records while it was in access. rather than fix
it in access and re-import it, is there an easy way to re-index the
records in mysql?
I am writing a small perl script that will write data to a Mysql
database. The SQL will need to be different based on whether or not the
e-mail address already exists in the database though. I coded something
that works, but I would like some feedback as to whether or not this is
the best way.
I am using a PHP script and a separate perl script, and they are
operating on the same MySQL database. I am fairly new to MySQL (and
programming in general), and I'm wondering if this could cause any
problems - especially during peak traffic times. Are there measures I
should be taking to
