Federated engine and comment???

2005-09-21 Thread Martijn Tonies
Hi there,

Did I just see in the documentation that the comment clause
is being misused to supply a connection string for the federated
engine?

If so, I sure hope it will be changed before the final 5.0 release.

comment is next to useless like this. It's already being misused
by InnoDB to describe the FK constraints...

What's wrong with introducing a new clause?

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle  MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Federated engine and comment???

2005-09-21 Thread Duncan Hill
On Wednesday 21 September 2005 11:23, Martijn Tonies typed:
 Hi there,

 Did I just see in the documentation that the comment clause
 is being misused to supply a connection string for the federated
 engine?

 If so, I sure hope it will be changed before the final 5.0 release.

 comment is next to useless like this. It's already being misused
 by InnoDB to describe the FK constraints...

 What's wrong with introducing a new clause?

The manual states:
The use of COMMENT for specifying the connection string is non-optimal and 
will likely change in MySQL 5.1. Keep this in mind when you use FEDERATED 
tables, because it means you'll need to make some modifications when that 
happens.

So I'd guess they know full well it's not the best way to do it.

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Federated engine and comment???

2005-09-21 Thread Duncan Hill
 On Wednesday 21 September 2005 11:23, Martijn Tonies typed:
  Hi there,
 
  Did I just see in the documentation that the comment clause
  is being misused to supply a connection string for the federated
  engine?
 
  If so, I sure hope it will be changed before the final 5.0 release.
 
  comment is next to useless like this. It's already being misused
  by InnoDB to describe the FK constraints...

Urm, where does it do that - my 4.1 server says
  CONSTRAINT `login_properties_ibfk_1` FOREIGN KEY (`prop_login_id`) 
REFERENCES `login_master` (`login_id`) ON DELETE CASCADE ON UPDATE CASCADE,
  CONSTRAINT `login_properties_ibfk_2` FOREIGN KEY (`ref_prop_name`) 
REFERENCES `login_properties_master` (`prop_name`) ON DELETE CASCADE ON 
UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Properties for a login'

nothing in the comment field about key constraints - or is that new in 5?

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Federated engine and comment???

2005-09-21 Thread Martijn Tonies


  On Wednesday 21 September 2005 11:23, Martijn Tonies typed:
   Hi there,
  
   Did I just see in the documentation that the comment clause
   is being misused to supply a connection string for the federated
   engine?
  
   If so, I sure hope it will be changed before the final 5.0 release.
  
   comment is next to useless like this. It's already being misused
   by InnoDB to describe the FK constraints...

 Urm, where does it do that - my 4.1 server says
   CONSTRAINT `login_properties_ibfk_1` FOREIGN KEY (`prop_login_id`)
 REFERENCES `login_master` (`login_id`) ON DELETE CASCADE ON UPDATE
CASCADE,
   CONSTRAINT `login_properties_ibfk_2` FOREIGN KEY (`ref_prop_name`)
 REFERENCES `login_properties_master` (`prop_name`) ON DELETE CASCADE ON
 UPDATE CASCADE
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Properties for a login'

 nothing in the comment field about key constraints - or is that new in 5?

show table status

eg:
InnoDB free: 10240 kB; (`card_id`) REFER `test/card`(`pkey`) ON DELETE NO
ACTION ON UPDATE NO ACTION; (`card_id`) REFER `test/card`(`pkey`) ON DELETE
NO ACTION ON UPDATE NO ACTION; (`trans_id`) REFER `test/trans`(`pkey`) ON
DELETE NO ACTION ON UPDATE NO ACTION


Where's my original comment, if any?

All in all, bad!

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle  MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Federated engine and comment???

2005-09-21 Thread Jim Winstead
On Wed, Sep 21, 2005 at 12:23:57PM +0200, Martijn Tonies wrote:
 Did I just see in the documentation that the comment clause
 is being misused to supply a connection string for the federated
 engine?
 
 If so, I sure hope it will be changed before the final 5.0 release.

This is fixed in 5.0.13, the documentation just hasn't caught up with
the change yet. The new syntax is CONNECTION = '...'.

Jim Winstead
MySQL Inc.

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Federated engine and comment???

2005-09-21 Thread Martijn Tonies
Hello Jim,


 On Wed, Sep 21, 2005 at 12:23:57PM +0200, Martijn Tonies wrote:
  Did I just see in the documentation that the comment clause
  is being misused to supply a connection string for the federated
  engine?
 
  If so, I sure hope it will be changed before the final 5.0 release.

 This is fixed in 5.0.13, the documentation just hasn't caught up with
 the change yet. The new syntax is CONNECTION = '...'.

Great, that's much better :-) :-)

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle  MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]