> > I think your problem lies in your SELECT *
> > If you look at the columnheaders below you get category_id twice.
> > I guess you have to specify your columns with aliases.
> >
> > /Johan
> >
>
> Hi Johan,
>
> Nope, if I change the column name to category_id1 then it's okay. See
> this: (apologies for the previous typo in the reproducible script)

Ehm, well, yeah - now this strikes me as a bad idea.

You're changing a base table column name to work around a non-issue
for a view definition?

Wouldn't it be better to get your view definition corrected? Which
is easy... :-)

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

> create table `ticket_master` (
> `ticket_id` int (5) NOT NULL AUTO_INCREMENT ,
> `category_id` int (5) NULL,
> PRIMARY KEY ( `ticket_id` ));
>
> Query OK, 0 rows affected
>
> create table `category_master` (
> `category_id` int (5) NOT NULL AUTO_INCREMENT ,
> `category_name` varchar (20) NULL,
> PRIMARY KEY ( `category_id` ));
>
> Query OK, 0 rows affected
>
> CREATE VIEW `v_tickets` AS
> (
> SELECT * FROM ticket_master tm, category_master cm
> WHERE tm.category_id = cm.category_id
> );
>
> ERROR 1060 : Duplicate column name 'category_id'
>
> alter table `category_master` ,change `category_id` `category_id1` int
> (5)   NOT NULL AUTO_INCREMENT ;
>
> CREATE VIEW `v_tickets` AS
> (
> SELECT * FROM ticket_master tm, category_master cm
> WHERE tm.category_id = cm.category_id1
> );
>
> Query OK, 0 rows affected


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

Reply via email to