Re: MySql plugin / driver bug
Re: MySql plugin / driver bug
- Subject: Re: MySql plugin / driver bug
- From: Mark Woollard <email@hidden>
- Date: Thu, 7 Jan 2010 00:13:24 +0000
Since the post I've replaced my manually created Eo with EO generated by many-many relationship creation between the two related EOs - this works fine - and clearly is the correct way to do what I want. However seems my fumbling as I get up to speed revealed the bug I mentioned.
Regards
Mark
On 7 Jan 2010, at 00:06, Chuck Hill wrote:
> Why does it need an ID field? Do the relationship keys not make it unique? Can you make it an EOGenericRecord?
>
>
> On Jan 6, 2010, at 2:07 PM, Mark Woollard wrote:
>
>> If you have an entity with no exposed properties incorrect SQL gets generated (mysql + plugin). I have an entity who's sole purpose is to map between two other entities, it contains no data itself, just two one:many relationships, and an id field, so three fields in all (id, and two for the relationships). This causes SQL to be generated 'select t0.relationship1Id, t0., t0.relationship2 FROM ...'. If I add a dummy data property to the entity you get 'select t0.relationship1Id, t0.dummy, t0.relationship2 FROM ...' generated. Seems that an assumption is being made that at least one exposed property will exist for the EO. Is this likely to be the plugin or the driver or WO itself?
>>
>> Thanks
>> Mark
>
>
> --
> Chuck Hill Senior Consultant / VP Development
>
> Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
> http://www.global-village.net/products/practical_webobjects
>
>
>
>
>
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden