[EMAIL PROTECTED] wrote:
Does this make better sense?
Yes, many thanks and regards,
Terence
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Terence <[EMAIL PROTECTED]> wrote on 10/07/2005 03:49:46 AM:
> Hi All,
>
> I get a duplicate column error on 5.0.13 when creating a view. Am I
> doing something wrong here or do I submit a bug report? This should be
> allowed as the col names
> are not duplicated.
>
> Reproduce:
>
> create ta
Hi Terence,
I guess I was a bit unclear on my comment on the
SELECT *. Anyway you did what I meant, i.e. changed
one of your category_id's so that the set
of columnnames ( as implied by the SELECT * ) becomes
unique. What happens is that your SELECT * becomes
SELECT ticket_id,category_id,category_
> > 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: (apolog
Johan Höök wrote:
Hi Terence,
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: (ap
Hi Terence,
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
SELECT * FROM ticket_master tm, category_master cm
WHERE tm.category_id = cm.category_id;
+---+
Hi All,
I get a duplicate column error on 5.0.13 when creating a view. Am I
doing something wrong here or do I submit a bug report? This should be
allowed as the col names
are not duplicated.
Reproduce:
create table `ticket_master` (
`ticket_id` int (5) NOT NULL AUTO_INCREMENT ,
`category_id