Hello List, I am having a real weird problem with MagritteGlorp. When I execute:
MyMagritteGlorpDescriptions createSchema.
Which by the way I have successfully executed many times before, I get a walk back stating: "Error: Object is not in the collection". Looking a little bit inside, I can see that the descriptions of the attributes of one of my classes, do not match it's current status (contains attributes that no longer belong to the class). That is, for instance that when DatabaseTable>>fieldNamed: is called, the fields attribute (which is the offending collection) contains an attribute (in my case "Field(BOOK.detailUrl") which does not exist in the class anymore. Attribute detailUrl was removed long ago. So the collection of descriptions seem old, and do not seem to reflect the current descriptions expressed by my class methods #descriptionXxxxx Is there any cache or something like that that should be reseted?
Hello List, I am having a real weird problem with MagritteGlorp. When I execute:
MyMagritteGlorpDescriptions createSchema. Which by the way I have successfully executed many timesbefore, I get a walk back stating: "Error: Object is not in the collection". Looking a little bit inside, I can see that the descriptions of the attributes of one of my classes, do not match it's current status (contains attributes that no longer belong to the class). That is, for instance that when DatabaseTable>>fieldNamed: is called, the fields attribute (which is the offending collection) contains an attribute (in my case "Field(BOOK.detailUrl") which does not exist in the class anymore. Attribute detailUrl was removed long ago. So the collection of descriptions seem old, and do not seem to reflect the current descriptions expressed by my class methods #descriptionXxxxx Is there any cache or something like that that should be reseted?
Try doing Book description to see if your class returns stale descriptions. If so, I think MADescriptionBuilder default flush should clean out the cache, then try again. Magritte caches descriptions and subscribes to several system events to keep track of when to update the cache, maybe you got out of sync somehow.
Ramon Leon http://onsmalltalk.com
Hello Ramón, Thank you for answering. Unfortunately the "MADescriptionBuilder default flush" did not change my problem. DatabaseTable>>fieldNamed: is still called with 'detailUrl' which does not exist as an attribute, method or description. I am attaching a SqueakDebug.log so may be you can see something that I dont. Thank you very much
r.
On 5/30/07, Ramon Leon ramon.leon@allresnet.com wrote:
Hello List, I am having a real weird problem with MagritteGlorp. When I execute:
MyMagritteGlorpDescriptions createSchema. Which by the way I have successfully executed many timesbefore, I get a walk back stating: "Error: Object is not in the collection". Looking a little bit inside, I can see that the descriptions of the attributes of one of my classes, do not match it's current status (contains attributes that no longer belong to the class). That is, for instance that when DatabaseTable>>fieldNamed: is called, the fields attribute (which is the offending collection) contains an attribute (in my case "Field(BOOK.detailUrl") which does not exist in the class anymore. Attribute detailUrl was removed long ago. So the collection of descriptions seem old, and do not seem to reflect the current descriptions expressed by my class methods #descriptionXxxxx Is there any cache or something like that that should be reseted?
Try doing Book description to see if your class returns stale descriptions. If so, I think MADescriptionBuilder default flush should clean out the cache, then try again. Magritte caches descriptions and subscribes to several system events to keep track of when to update the cache, maybe you got out of sync somehow.
Ramon Leon http://onsmalltalk.com
May be an important thing to clarify is the context. I run on the latest developer image from Damien. When I load MagritteGlorp from squeksource and it asks me "Load older dependency Magritte-Model-lr.239" I answer NO. But again, I did not have problems before.
On 5/30/07, Ramiro Diaz Trepat ramirodt@gmail.com wrote:
Hello Ramón, Thank you for answering. Unfortunately the "MADescriptionBuilder default flush" did not change my problem. DatabaseTable>>fieldNamed: is still called with 'detailUrl' which does not exist as an attribute, method or description. I am attaching a SqueakDebug.log so may be you can see something that I dont. Thank you very much
r.
On 5/30/07, Ramon Leon ramon.leon@allresnet.com wrote:
Hello List, I am having a real weird problem with MagritteGlorp. When I execute:
MyMagritteGlorpDescriptions createSchema. Which by the way I have successfully executed many timesbefore, I get a walk back stating: "Error: Object is not in the collection". Looking a little bit inside, I can see that the descriptions of the attributes of one of my classes, do not match it's current status (contains attributes that no longer belong to the class). That is, for instance that when DatabaseTable>>fieldNamed: is called, the fields attribute (which is the offending collection) contains an attribute (in my case "Field(BOOK.detailUrl") which does not exist in the class anymore. Attribute detailUrl was removed long ago. So the collection of descriptions seem old, and do not seem to reflect the current descriptions expressed by my class methods #descriptionXxxxx Is there any cache or something like that that should be reseted?
Try doing Book description to see if your class returns stale descriptions. If so, I think MADescriptionBuilder default flush should clean out the cache, then try again. Magritte caches descriptions and subscribes to several system events to keep track of when to update the cache, maybe you got out of sync somehow.
Ramon Leon http://onsmalltalk.com
Sorry, the previous debug log was old, this is the correct one.
On 5/30/07, Ramiro Diaz Trepat ramirodt@gmail.com wrote:
Hello Ramón, Thank you for answering. Unfortunately the "MADescriptionBuilder default flush" did not change my problem. DatabaseTable>>fieldNamed: is still called with 'detailUrl' which does not exist as an attribute, method or description. I am attaching a SqueakDebug.log so may be you can see something that I dont. Thank you very much
r.
On 5/30/07, Ramon Leon ramon.leon@allresnet.com wrote:
Hello List, I am having a real weird problem with MagritteGlorp. When I execute:
MyMagritteGlorpDescriptions createSchema. Which by the way I have successfully executed many timesbefore, I get a walk back stating: "Error: Object is not in the collection". Looking a little bit inside, I can see that the descriptions of the attributes of one of my classes, do not match it's current status (contains attributes that no longer belong to the class). That is, for instance that when DatabaseTable>>fieldNamed: is called, the fields attribute (which is the offending collection) contains an attribute (in my case "Field(BOOK.detailUrl") which does not exist in the class anymore. Attribute detailUrl was removed long ago. So the collection of descriptions seem old, and do not seem to reflect the current descriptions expressed by my class methods #descriptionXxxxx Is there any cache or something like that that should be reseted?
Try doing Book description to see if your class returns stale descriptions. If so, I think MADescriptionBuilder default flush should clean out the cache, then try again. Magritte caches descriptions and subscribes to several system events to keep track of when to update the cache, maybe you got out of sync somehow.
Ramon Leon http://onsmalltalk.com
squeak-dev@lists.squeakfoundation.org
-
Ramiro Diaz Trepat -
Ramon Leon