Re: Different behavior from ERMD2WEditToOneTypeAhead
> On Oct 10, 2016, at 12:20 PM, Fabian Peters wrote:
>
> Hi Tim,
>
>> One other comment. The only downside to this is that it restricts the search
>> string the user can type to a specific attribute instead of the broader
>> concatenated representation which provided a “fuzzier” search. And
>> obviously, requires communication with the user about what they can expect
>> to return matching results.
>
> You can specify multiple attributes, which will then be ORed, e.g.:
>
> 100 : smartRelationship.destinationEntity.name = ‘Product' => searchKey =
> ("productNumber", "title", "comment", "product.supplier.name")"
> [com.webobjects.directtoweb.Assignment]
>
> The advantage being that this allows you to qualify via SQL, not in-memory.
This is great.
keyWhenRelationship is still needed to designate what the user sees in the
search result list.
I appreciate the info - I was having a hard time this week finding the time to
research the changes. Good stuff.
Tim
>
> Also, there's a "log.warn()" statement that should inform you if the
> attribute couldn't be resolved via the model. I've just checked that it's
> getting called, but it doesn't log anything. Maybe that's due to the changes
> to the logging system. I'll have a look at it.
>
> Fabian
>
>> Tim
>>
>>> On Oct 7, 2016, at 11:54 AM, T Worman wrote:
>>>
>>> Fabian:
>>>
>>> Nice! That rule did the trick. Thanks for responding - kept me from having
>>> to dig more. So, I have two rules now that look like:
>>>
>>> 100 : smartRelationship.destinationEntity.name = ‘Product' =>
>>> keyWhenRelationship = "d2wProductDisplayWhenRelationship"
>>> [com.webobjects.directtoweb.Assignment]
>>> 100 : smartRelationship.destinationEntity.name = ‘Product' => searchKey =
>>> “productNumber" [com.webobjects.directtoweb.Assignment]
>>>
>>> Where ‘d2wProductDisplayWhenRelationship’ is a method that returns a nice
>>> user-readable string for the objects in the search results.
>>>
>>> Thanks for the assist!
>>>
>>> Tim
>>> UCLA GSE&IS
>>>
On Oct 6, 2016, at 11:03 PM, Fabian Peters wrote:
Hi Tim,
ERMD2WEditToOneTypeAhead got a few changes from me, including one to use
the ERMD2WAttributeQueryDelegate. The change aimed to preserve the
original behaviour, but looking at the code it may be that it doesn't when
the data source being used is an EODatabaseDataSource.
Using a rule like this should sort it out at any rate:
100 : smartRelationship.destinationEntity.name = 'Product' => searchKey =
"productNumber" [com.webobjects.directtoweb.Assignment]
If it does, I'd still like to have another look at why the default
behaviour is not being preserved…
Fabian
> Am 06.10.2016 um 23:56 schrieb T Worman :
>
> Hello All:
>
> I have a relationship sth like:
>
> Product(productId) <-> LineItem(productId)
>
> I am using ERMD2WEditToOneTypeAhead on the attribute
> Product.productNumber on a CreateLineItem page. But I’ve also got a rule
> for keyWhenRelationship like:
>
> 100 : smartRelationship.destinationEntity.name = ‘Product' =>
> keyWhenRelationship = "d2wProductDisplayWhenRelationship"
> [com.webobjects.directtoweb.Assignment]
>
> where Product.d2wProductDisplayWhenRelationship returns a concatenated
> string that gives a more complete description of the product. Previously,
> this worked to only display items where Product.productNumber matched the
> string inserted by the user. Now it only works correctly if
> keyWhenRelationship=productNumber. The problem with this is that it
> doesn’t give the user enough feedback about the search results.
>
> Also, the behavior I’m seeing is that a whole list of Product objects are
> returned that do not match Product.productNumber. Which is confusing.
>
> I haven’t had a chance to look through recent commits yet but plan to do
> that later today. Just wanted to check and see - does anybody have any
> insight about this?
>
> Tim
> UCLA GSE&IS
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
>
> This email sent to lists.fab...@e-lumo.com
>>>
>>>
>>> ___
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com
>>>
>>> This email sent to li...@thetimmy.com
>>
>>
>> ___
>> Do not post admi
Re: Different behavior from ERMD2WEditToOneTypeAhead
Hi Tim,
> One other comment. The only downside to this is that it restricts the search
> string the user can type to a specific attribute instead of the broader
> concatenated representation which provided a “fuzzier” search. And obviously,
> requires communication with the user about what they can expect to return
> matching results.
You can specify multiple attributes, which will then be ORed, e.g.:
100 : smartRelationship.destinationEntity.name = ‘Product' => searchKey =
("productNumber", "title", "comment", "product.supplier.name")"
[com.webobjects.directtoweb.Assignment]
The advantage being that this allows you to qualify via SQL, not in-memory.
Also, there's a "log.warn()" statement that should inform you if the attribute
couldn't be resolved via the model. I've just checked that it's getting called,
but it doesn't log anything. Maybe that's due to the changes to the logging
system. I'll have a look at it.
Fabian
> Tim
>
>> On Oct 7, 2016, at 11:54 AM, T Worman wrote:
>>
>> Fabian:
>>
>> Nice! That rule did the trick. Thanks for responding - kept me from having
>> to dig more. So, I have two rules now that look like:
>>
>> 100 : smartRelationship.destinationEntity.name = ‘Product' =>
>> keyWhenRelationship = "d2wProductDisplayWhenRelationship"
>> [com.webobjects.directtoweb.Assignment]
>> 100 : smartRelationship.destinationEntity.name = ‘Product' => searchKey =
>> “productNumber" [com.webobjects.directtoweb.Assignment]
>>
>> Where ‘d2wProductDisplayWhenRelationship’ is a method that returns a nice
>> user-readable string for the objects in the search results.
>>
>> Thanks for the assist!
>>
>> Tim
>> UCLA GSE&IS
>>
>>> On Oct 6, 2016, at 11:03 PM, Fabian Peters wrote:
>>>
>>> Hi Tim,
>>>
>>> ERMD2WEditToOneTypeAhead got a few changes from me, including one to use
>>> the ERMD2WAttributeQueryDelegate. The change aimed to preserve the original
>>> behaviour, but looking at the code it may be that it doesn't when the data
>>> source being used is an EODatabaseDataSource.
>>>
>>> Using a rule like this should sort it out at any rate:
>>>
>>> 100 : smartRelationship.destinationEntity.name = 'Product' => searchKey =
>>> "productNumber" [com.webobjects.directtoweb.Assignment]
>>>
>>> If it does, I'd still like to have another look at why the default
>>> behaviour is not being preserved…
>>>
>>> Fabian
>>>
Am 06.10.2016 um 23:56 schrieb T Worman :
Hello All:
I have a relationship sth like:
Product(productId) <-> LineItem(productId)
I am using ERMD2WEditToOneTypeAhead on the attribute Product.productNumber
on a CreateLineItem page. But I’ve also got a rule for keyWhenRelationship
like:
100 : smartRelationship.destinationEntity.name = ‘Product' =>
keyWhenRelationship = "d2wProductDisplayWhenRelationship"
[com.webobjects.directtoweb.Assignment]
where Product.d2wProductDisplayWhenRelationship returns a concatenated
string that gives a more complete description of the product. Previously,
this worked to only display items where Product.productNumber matched the
string inserted by the user. Now it only works correctly if
keyWhenRelationship=productNumber. The problem with this is that it
doesn’t give the user enough feedback about the search results.
Also, the behavior I’m seeing is that a whole list of Product objects are
returned that do not match Product.productNumber. Which is confusing.
I haven’t had a chance to look through recent commits yet but plan to do
that later today. Just wanted to check and see - does anybody have any
insight about this?
Tim
UCLA GSE&IS
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
This email sent to lists.fab...@e-lumo.com
>>>
>>
>>
>> ___
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com
>>
>> This email sent to li...@thetimmy.com
>
>
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
>
> This email sent to lists.fab...@e-lumo.com
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing li
Re: Different behavior from ERMD2WEditToOneTypeAhead
One other comment. The only downside to this is that it restricts the search string the user can type to a specific attribute instead of the broader concatenated representation which provided a “fuzzier” search. And obviously, requires communication with the user about what they can expect to return matching results. Tim > On Oct 7, 2016, at 11:54 AM, T Worman wrote: > > Fabian: > > Nice! That rule did the trick. Thanks for responding - kept me from having to > dig more. So, I have two rules now that look like: > > 100 : smartRelationship.destinationEntity.name = ‘Product' => > keyWhenRelationship = "d2wProductDisplayWhenRelationship" > [com.webobjects.directtoweb.Assignment] > 100 : smartRelationship.destinationEntity.name = ‘Product' => searchKey = > “productNumber" [com.webobjects.directtoweb.Assignment] > > Where ‘d2wProductDisplayWhenRelationship’ is a method that returns a nice > user-readable string for the objects in the search results. > > Thanks for the assist! > > Tim > UCLA GSE&IS > >> On Oct 6, 2016, at 11:03 PM, Fabian Peters wrote: >> >> Hi Tim, >> >> ERMD2WEditToOneTypeAhead got a few changes from me, including one to use the >> ERMD2WAttributeQueryDelegate. The change aimed to preserve the original >> behaviour, but looking at the code it may be that it doesn't when the data >> source being used is an EODatabaseDataSource. >> >> Using a rule like this should sort it out at any rate: >> >> 100 : smartRelationship.destinationEntity.name = 'Product' => searchKey = >> "productNumber" [com.webobjects.directtoweb.Assignment] >> >> If it does, I'd still like to have another look at why the default behaviour >> is not being preserved… >> >> Fabian >> >>> Am 06.10.2016 um 23:56 schrieb T Worman : >>> >>> Hello All: >>> >>> I have a relationship sth like: >>> >>> Product(productId) <-> LineItem(productId) >>> >>> I am using ERMD2WEditToOneTypeAhead on the attribute Product.productNumber >>> on a CreateLineItem page. But I’ve also got a rule for keyWhenRelationship >>> like: >>> >>> 100 : smartRelationship.destinationEntity.name = ‘Product' => >>> keyWhenRelationship = "d2wProductDisplayWhenRelationship" >>> [com.webobjects.directtoweb.Assignment] >>> >>> where Product.d2wProductDisplayWhenRelationship returns a concatenated >>> string that gives a more complete description of the product. Previously, >>> this worked to only display items where Product.productNumber matched the >>> string inserted by the user. Now it only works correctly if >>> keyWhenRelationship=productNumber. The problem with this is that it doesn’t >>> give the user enough feedback about the search results. >>> >>> Also, the behavior I’m seeing is that a whole list of Product objects are >>> returned that do not match Product.productNumber. Which is confusing. >>> >>> I haven’t had a chance to look through recent commits yet but plan to do >>> that later today. Just wanted to check and see - does anybody have any >>> insight about this? >>> >>> Tim >>> UCLA GSE&IS >>> ___ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com >>> >>> This email sent to lists.fab...@e-lumo.com >> > > > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com > > This email sent to li...@thetimmy.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Different behavior from ERMD2WEditToOneTypeAhead
Fabian: Nice! That rule did the trick. Thanks for responding - kept me from having to dig more. So, I have two rules now that look like: 100 : smartRelationship.destinationEntity.name = ‘Product' => keyWhenRelationship = "d2wProductDisplayWhenRelationship" [com.webobjects.directtoweb.Assignment] 100 : smartRelationship.destinationEntity.name = ‘Product' => searchKey = “productNumber" [com.webobjects.directtoweb.Assignment] Where ‘d2wProductDisplayWhenRelationship’ is a method that returns a nice user-readable string for the objects in the search results. Thanks for the assist! Tim UCLA GSE&IS > On Oct 6, 2016, at 11:03 PM, Fabian Peters wrote: > > Hi Tim, > > ERMD2WEditToOneTypeAhead got a few changes from me, including one to use the > ERMD2WAttributeQueryDelegate. The change aimed to preserve the original > behaviour, but looking at the code it may be that it doesn't when the data > source being used is an EODatabaseDataSource. > > Using a rule like this should sort it out at any rate: > > 100 : smartRelationship.destinationEntity.name = 'Product' => searchKey = > "productNumber" [com.webobjects.directtoweb.Assignment] > > If it does, I'd still like to have another look at why the default behaviour > is not being preserved… > > Fabian > >> Am 06.10.2016 um 23:56 schrieb T Worman : >> >> Hello All: >> >> I have a relationship sth like: >> >> Product(productId) <-> LineItem(productId) >> >> I am using ERMD2WEditToOneTypeAhead on the attribute Product.productNumber >> on a CreateLineItem page. But I’ve also got a rule for keyWhenRelationship >> like: >> >> 100 : smartRelationship.destinationEntity.name = ‘Product' => >> keyWhenRelationship = "d2wProductDisplayWhenRelationship" >> [com.webobjects.directtoweb.Assignment] >> >> where Product.d2wProductDisplayWhenRelationship returns a concatenated >> string that gives a more complete description of the product. Previously, >> this worked to only display items where Product.productNumber matched the >> string inserted by the user. Now it only works correctly if >> keyWhenRelationship=productNumber. The problem with this is that it doesn’t >> give the user enough feedback about the search results. >> >> Also, the behavior I’m seeing is that a whole list of Product objects are >> returned that do not match Product.productNumber. Which is confusing. >> >> I haven’t had a chance to look through recent commits yet but plan to do >> that later today. Just wanted to check and see - does anybody have any >> insight about this? >> >> Tim >> UCLA GSE&IS >> ___ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com >> >> This email sent to lists.fab...@e-lumo.com > ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Different behavior from ERMD2WEditToOneTypeAhead
Hi Tim, ERMD2WEditToOneTypeAhead got a few changes from me, including one to use the ERMD2WAttributeQueryDelegate. The change aimed to preserve the original behaviour, but looking at the code it may be that it doesn't when the data source being used is an EODatabaseDataSource. Using a rule like this should sort it out at any rate: 100 : smartRelationship.destinationEntity.name = 'Product' => searchKey = "productNumber" [com.webobjects.directtoweb.Assignment] If it does, I'd still like to have another look at why the default behaviour is not being preserved… Fabian > Am 06.10.2016 um 23:56 schrieb T Worman : > > Hello All: > > I have a relationship sth like: > > Product(productId) <-> LineItem(productId) > > I am using ERMD2WEditToOneTypeAhead on the attribute Product.productNumber on > a CreateLineItem page. But I’ve also got a rule for keyWhenRelationship like: > > 100 : smartRelationship.destinationEntity.name = ‘Product' => > keyWhenRelationship = "d2wProductDisplayWhenRelationship" > [com.webobjects.directtoweb.Assignment] > > where Product.d2wProductDisplayWhenRelationship returns a concatenated string > that gives a more complete description of the product. Previously, this > worked to only display items where Product.productNumber matched the string > inserted by the user. Now it only works correctly if > keyWhenRelationship=productNumber. The problem with this is that it doesn’t > give the user enough feedback about the search results. > > Also, the behavior I’m seeing is that a whole list of Product objects are > returned that do not match Product.productNumber. Which is confusing. > > I haven’t had a chance to look through recent commits yet but plan to do that > later today. Just wanted to check and see - does anybody have any insight > about this? > > Tim > UCLA GSE&IS > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com > > This email sent to lists.fab...@e-lumo.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Different behavior from ERMD2WEditToOneTypeAhead
Thanks Flavio. I tried it but it did not work. I am still getting a full list of objects that do not match the the value entered by the user. Bummer - this used to work. Will have to figure out if any recent changes have impacted this. Tim > On Oct 6, 2016, at 4:26 PM, Flavio Donadio wrote: > > Tim, > > > I believe you need to change that rule to use an ERDDelayedAssignment, not a > plain Assignment. But I might be wrong. > > > Cheers, > Flavio > >> On 06/10/2016, at 18:56, T Worman wrote: >> >> Hello All: >> >> I have a relationship sth like: >> >> Product(productId) <-> LineItem(productId) >> >> I am using ERMD2WEditToOneTypeAhead on the attribute Product.productNumber >> on a CreateLineItem page. But I’ve also got a rule for keyWhenRelationship >> like: >> >> 100 : smartRelationship.destinationEntity.name = ‘Product' => >> keyWhenRelationship = "d2wProductDisplayWhenRelationship" >> [com.webobjects.directtoweb.Assignment] >> >> where Product.d2wProductDisplayWhenRelationship returns a concatenated >> string that gives a more complete description of the product. Previously, >> this worked to only display items where Product.productNumber matched the >> string inserted by the user. Now it only works correctly if >> keyWhenRelationship=productNumber. The problem with this is that it doesn’t >> give the user enough feedback about the search results. >> >> Also, the behavior I’m seeing is that a whole list of Product objects are >> returned that do not match Product.productNumber. Which is confusing. >> >> I haven’t had a chance to look through recent commits yet but plan to do >> that later today. Just wanted to check and see - does anybody have any >> insight about this? >> >> Tim >> UCLA GSE&IS >> ___ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/flavio%40donadio.com.br >> >> This email sent to fla...@donadio.com.br > ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Different behavior from ERMD2WEditToOneTypeAhead
Tim, I believe you need to change that rule to use an ERDDelayedAssignment, not a plain Assignment. But I might be wrong. Cheers, Flavio > On 06/10/2016, at 18:56, T Worman wrote: > > Hello All: > > I have a relationship sth like: > > Product(productId) <-> LineItem(productId) > > I am using ERMD2WEditToOneTypeAhead on the attribute Product.productNumber on > a CreateLineItem page. But I’ve also got a rule for keyWhenRelationship like: > > 100 : smartRelationship.destinationEntity.name = ‘Product' => > keyWhenRelationship = "d2wProductDisplayWhenRelationship" > [com.webobjects.directtoweb.Assignment] > > where Product.d2wProductDisplayWhenRelationship returns a concatenated string > that gives a more complete description of the product. Previously, this > worked to only display items where Product.productNumber matched the string > inserted by the user. Now it only works correctly if > keyWhenRelationship=productNumber. The problem with this is that it doesn’t > give the user enough feedback about the search results. > > Also, the behavior I’m seeing is that a whole list of Product objects are > returned that do not match Product.productNumber. Which is confusing. > > I haven’t had a chance to look through recent commits yet but plan to do that > later today. Just wanted to check and see - does anybody have any insight > about this? > > Tim > UCLA GSE&IS > ___ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/flavio%40donadio.com.br > > This email sent to fla...@donadio.com.br ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
