This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello All, Somehow I've tweaked something with the model and/or the context, and I can NOT get any results from performing a Find or a FindOne... I've added a Tracelogger and looked at the code and I see now that it's NOT opening a good cursor. Before when I was testing the sql line was something to the effect of: Now it's trying to open a "NULL" cursor... (to the effect of:) Which I think is the main reason why I'm not getting any results from the query. I've tried to delete the model and re-add a new one, but that didn't help... What could I have changed to make theis change in the sql happen??? Any Ideas out there??? Kevin Orcutt
|
|
|
|
|
We're pretty certain the OPEN NULL FOR is a bug in the logger, not a bug in the actual generated command. So I don't think the SQL has actually changed (or at least not in that regard). All of our Oracle test cases are still passing (despite being logged as OPEN NULL FOR) so we're confident that we're not really opening bad cursors and that this isn't the source of your problem. My guess would be that there's some sort of configuration issue, e.g. you might have updated a connection string to point at a temporary test database and forgotten to set it back. Is that possible? |
|
|
|
