Okay. So I wrote a test case with similar behavior and it worked correctly, but the difference between the test case objects and my objects is that all of the test case objects are active records that get saved, not just the top level object as in my code.
So I guess there is no bug, I just do not understand what I am doing, which is what I was expecting to be the case anyway. So I guess my question is, do I need to make every object I am saving into a subclass of SDActiveRecord and go through everything and save everything, or should I be able to have, in my example code, the class Test be the only SDActiveRecord subclass and only worry about saving instances of Test? On Wed, Jun 29, 2011 at 6:17 PM, Ramon Leon <[email protected]>wrote: > On 06/29/2011 02:55 PM, David Zmick wrote: > >> >> Do you want me to create a test in the actual test classes for >> Sandstonedb using the mom dad kid objects or can I do something like this? >> > > If you can use the existing mocks, i.e. the man woman child classes, and > make it fail in a workspace like you just did, that would be very helpful. > Look at the existing testDictionaryKeys and build a similar one in the test > class and get it to fail. Send me the failing test. If you can do it in a > workspace, you can do it in a test, but I'd start with the test and forget > the workspace all together. You may find a bug, or you may find you were > wrong. > > If you don't reply with a failing test, I may or may not find some time > tonight to look into your examples, but if you need/want it fixed fast, send > me a failing test. > > > -- > Ramon Leon > http://onsmalltalk.com > > -- David Zmick [email protected]
