Just to let you know what I ended up with: I created my own EditYNBoolean and QueryYNBoolean property level component.
Using a custom read/write format on the attribute worked almost... The format is also being used in the where-clause against the database when the "use for locking" flag is set in the EOModel on that particular attribute. And in that case Oracle throws up. Oh well. Anyway my problem is solved and I am busy finding more things to do that I am going to ask here :-))) Have a nice day ---markus--- On 19.03.2011, at 15:23, Ramsey Gurley wrote: > I think either you could use an attribute read/write format > > http://developer.apple.com/legacy/mac/library/#documentation/WebObjects/UsingEOModeler/4WorkingWithAttributes/WorkingWithAttributes.html%23//apple_ref/doc/uid/TP30001018-CH204-BABCHIIF > > Or you could model a custom boolean prototype using ERAttributeExtension. > > Ramsey > > On Mar 19, 2011, at 5:44 AM, Markus Ruggiero wrote: > >> >> On 16.03.2011, at 14:53, Markus Ruggiero wrote: >> >>> I have a (Oracle) table where boolean attributes are defined as char(1) >>> with possible values "Y", "N", or NULL (is equivalent to "N"). Due to 3rd >>> party apps I cannot change the database to char(5) and use the standard >>> modelling technique of toString() and valueOf() with Strings "true" and >>> "false" in the DB. How can I model such an attribute in a D2W compliant >>> way? I have tried the following: rename the attribute in EOModel to >>> "publishedYN" but leave the column name "published" and added published() >>> and setPublished() to the business logic. This works and I can e.g. use >>> ERD2WCustomeQueryBoolean in my query page configuration. However when I >>> click query I get the following exception: >>> >>> java.lang.IllegalStateException: sqlStringForKeyValueQualifier: attempt to >>> generate SQL for com.webobjects.eocontrol.EOKeyValueQualifier (publish = >>> (java.lang.Boolean)'false') failed because attribute identified by key >>> 'publish' was not reachable from from entity 'TechdocType' >>> >>> Yes, there is no such attribute and thus the crash makes sense. How can I >>> fix this? Any ideas? Unfortunately it is not possible to extend >>> java.lang.Boolean >>> >> >> Nobody? Really? Someone must have had the same or a similar issue! How did >> you solve this? >> >> Oh well, I seem to have found the ultimate not-yet-solved-issue(TM) >> >> Fun to you and have a great weekend >> ---markus--- >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/webobjects-dev/ramseygurley%40gmail.com >> >> This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
