Hello again, we've been working with the above mentioned approach for a couple of days now and we're still discovering serious problems. The replacement of empty strings works (more or less) but when objects are queried with an empty string the SECOND time (inside a transaction), we don't get any objects anymore. This is obviously because CAR caches the objects and since they have been "translated" to empty strings in the first run, the second query which still queries for our replacement string ($$$) doesn't find any objects anymore. Again the question: How do ORACLE users work with empty strings?? I can't imagine that nobody had that issue before!?
Another strange issue: I would have expected that when I use nested transactions (TransactionScope inside TransactionScopes), that the whole bunch of data is written to the DB when the OUTERMOST transaction is committed. But as far as I can see the transaction already gets transferred to the DB when the INNERMOST transaction is committed. Is this intended? So therefore it is not possible to use nested transactions? (At least it doesn't makes sense the way it looks right now...) Thanks again... G. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
