I'm running Castor 0.9.4.3 . Moving to 0.9.6 caused some minor issues, and I've not the time to drop the latest Castor in and do full regression testing.
I have an issue where if I do a select with little or no parameters I get very strange results. First of all, there are only 29 records total for the table I'm pulling from. If I do a straight select (using OQL, e.g. "SELECT o FROM ObjectName") I get not 29, but 30 records. The first record is being placed as the 30th and final record. If I place a WHERE clause on my OQL, which should take away one of the 29 records leaving 28, I still have 30 records being pulled from my OQL Query. Stranger still, if I place an ORDER BY on a string field to alphabetize the resultset, it pulls not 28, 29, or 30, but 34. There doesn't seem to be any sort of pattern to this particular set. For reference, not that it will help, here are the primary keys of the set of 34: 1: 930016 2: 1961509 3: 589902 4: 593437 5: 586982 6: 584062 7: 5002 8: 85 9: 84 10: 99081 11: 83 12: 99081 <-- repeat of 10th 13: 83 <-- repeat of 11th 14: 81 15: 501478 16: 81 <-- repeat of 14th 17: 87 18: 325893 19: 87 <-- repeat of 17th 20: 86 21: 1064890 22: 487895 23: 490621 24: 487895 <-- repeat of 22nd 25: 863602 26: 919613 27: 80 28: 544421 29: 781975 30: 796335 31: 781975 <-- repeat of 29 32: 785875 33: 532108 34: 535028 After tracking this down, it appears to be caused by a "many-key" type mapping, which in this case is a map to a linking table with another table/object to make a many-to-many type relationship. Removing this fixes the above query, but it then requires that this many-to-many relationship be handled manually. Is there any known resolution for this issue? -Ron ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
