Michael Stassen wrote:
zzapper wrote:
> Hi,
> Final whinge: I wish the mysql website made it a little clearer
which > features are recent additions, I suggested color coding.
Philippe Poelvoorde wrote:
I reckon, it's a bit hidden in the middle :
"Starting with MySQL 4.0.4, you can also perfo
On Wed, 27 Apr 2005 09:51:41 -0400, wrote:
My subject is a bit of a misnomer in fact the Where refers to multiple tables
but the delete is just
from one table, nevertheless my query worked super-dandy in 4.1 (on my test
rig) and failed on the
live server 3.23.47 . that's why I couldn't work out
zzapper wrote:
> Hi,
> Final whinge: I wish the mysql website made it a little clearer
which > features are recent additions, I suggested color coding.
Philippe Poelvoorde wrote:
I reckon, it's a bit hidden in the middle :
"Starting with MySQL 4.0.4, you can also perform UPDATE operations
th
zzapper wrote:
On Wed, 27 Apr 2005 09:50:37 +0100, wrote:
zzapper wrote:
On Tue, 26 Apr 2005 23:22:46 +0100, wrote:
Hi,
The following query runs fine in recent versions of mysql 4.1x etc
delete from t2 using tbl_User as t1,tbl_UserTopic as t2 where
(t1.txtemail='[EMAIL PROTECTED]')
and (t1.int
From: "zzapper"
> Final whinge: I wish the mysql website made it a little clearer which
features are recent
> additions, I suggested color coding.
1) Someone from MySQL AB mentioned here recently that they are working on a
new system to keep track of differences between versions for the
documenta
Hi,
Final whinge: I wish the mysql website made it a little clearer which features
are recent
additions, I suggested color coding.
BTW regards multi table deletes there's something nasty there between 4.0 and
4.1
--
zzapper
vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?"
On Wed, 27 Apr 2005 09:50:37 +0100, wrote:
>zzapper wrote:
>> On Tue, 26 Apr 2005 23:22:46 +0100, wrote:
>>
>>
>>>Hi,
>>>
>>>The following query runs fine in recent versions of mysql 4.1x etc
>>>
>>>delete from t2 using tbl_User as t1,tbl_UserTopic as t2 where
>>>(t1.txtemail='[EMAIL PROTECTE
zzapper wrote:
On Tue, 26 Apr 2005 23:22:46 +0100, wrote:
Hi,
The following query runs fine in recent versions of mysql 4.1x etc
delete from t2 using tbl_User as t1,tbl_UserTopic as t2 where
(t1.txtemail='[EMAIL PROTECTED]')
and (t1.intID = t2.intID);
But not in 3.23.47 I can't find any referenc
On Tue, 26 Apr 2005 23:22:46 +0100, wrote:
>Hi,
>
>The following query runs fine in recent versions of mysql 4.1x etc
>
>delete from t2 using tbl_User as t1,tbl_UserTopic as t2 where
>(t1.txtemail='[EMAIL PROTECTED]')
>and (t1.intID = t2.intID);
>
>But not in 3.23.47 I can't find any reference i
Hi!
On Friday 01 November 2002 15:03, Jon Frisby wrote:
> Why not just do:
> DELETE FROM MyChannels;
> DELETE FROM MyPackages;
>
> If you're concerned about atomicity, simply acquire a lock on both
> tables at once first.
Exactly, it was my concern. I'm not using MySQL tables with transaction
sup
If you do:
SELECT * FROM MyChannels, MyPackages;
Then you should also get nothing because what you're asking the database
to do is to perform a cartesian cross of the rows in both tables. Since
there's no row in one of the tables, the cross will contain no rows.
Ideally one could do:
DELETE FR
al Message -
From: "Oladapo Carew" <[EMAIL PROTECTED]>
To: "Anibal Cascais Santos" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, June 20, 2002 4:45 PM
Subject: RE: multi-table delete
>
> I think you have to specify the join from the cust
I think you have to specify the join from the customers table to the other
tables ..
-Original Message-
From: Anibal Cascais Santos [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 20, 2002 3:38 PM
To: [EMAIL PROTECTED]
Subject: multi-table delete
Hi,
I'm rather new to mySQL, so maybe
Hi!
I still can not reproduce your case.
I first ran this script:
create database xx;
use xx;
CREATE TABLE `t1` (
`titre` char(80) NOT NULL default '',
`numeropost` mediumint(8) unsigned NOT NULL auto_increment,
`ouvert` tinyint(1) unsigned NOT NULL default '1',
`date` datetime N
Hi!
Thank you for your test case.
However, with latest 4.0.2 code I am getting correct results with
it. Difference in number of rows in select and delete are stemming
from the fact that select reports number of rows in result set, while
delete reports total number of rows deleted.
These are r
- Original Message -
From: "Jocelyn Fournier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, May 25, 2002 3:35 PM
Subject: Re: multi-table delete bug
Hi,
Yes, you're right, but to see
Thank you for your report.
We shall take a look at it.
--
Regards,
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www
OK, I sent in something I hope will be useful.
# PROBLEM SUMMARY ###
Two problems seen with multi-table delete:
1) After a multi-table delete, first query of the second table
referenced in
the delete results in ERROR 1032. Subsequent queries are fine. Happens
with
BDB and InnoDB.
hi!
> "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes:
Sinisa> Becky McElroy writes:
>> Two questions regarding multi-table operations:
>>
>> 1) I've got multi-table delete working with a couple of BDB tables,
>> where it's properly deleting from one or both tables, and all
>> po
Becky McElroy writes:
> Thank you for your response and the info.
>
> Actually I was using 4.0.1 which I downloaded a couple of days ago:
>
> [beckymcelroy@indigo bhm]$ rpm -qa | grep SQL
> MySQL-Max-4.0.1-2
> MySQL-client-4.0.1-2
> MySQL-4.0.1-2
> [beckymcelroy@indigo bhm]$
>
[skip]
> --
> B
Thank you for your response and the info.
Actually I was using 4.0.1 which I downloaded a couple of days ago:
[beckymcelroy@indigo bhm]$ rpm -qa | grep SQL
MySQL-Max-4.0.1-2
MySQL-client-4.0.1-2
MySQL-4.0.1-2
[beckymcelroy@indigo bhm]$
Here's what I did:
mysql>
mysql> select * from cnam1;
+---
Becky McElroy writes:
> Two questions regarding multi-table operations:
>
> 1) I've got multi-table delete working with a couple of BDB tables,
> where it's properly deleting from one or both tables, and all
> possibilities of the delete criteria are being exersized. After the
> multi-table dele
22 matches
Mail list logo
