Concerning NH-2527: Using a disposed object is against all rules, so Oracle would reject such an issue, even if other DataProviders allow it.
Concerning NH-2792: I don't know the specifications of DataProviders, so I don't know if they shouldn't throw exceptions in that cases. Most likely this isn't specified at all, so any implementation is "correct" and Oracle would reject the issue. So no, I didn't. On Jul 18, 3:01 pm, Fabio Maulo <[email protected]> wrote: > Cremor, > just to satisfy my curiosity, > did you send the issue even to Oracle and/or Microsoft with > the incongruousness with all others DataProviders implementations ? > how they have classified the issue ? > > > > > > > > > > On Fri, Jul 15, 2011 at 2:38 AM, cremor <[email protected]> wrote: > > In the past few months I have reported several bugs that either throw > > an exception directly in NHibernate code or generate invalid SQL > > queries so that the data provider throws an exception. I have created > > all this issues with priority "critical" because the description of > > "critical" says "Crashes, loss of data, severe memory leak." (an > > exception is a crash at least). > > > One of this bugs (https://nhibernate.jira.com/browse/NH-2527) was even > > changed to "Minor" ("Minor loss of function, or other problem where > > easy workaround is present.") although there is NO workaround present. > > > Could you please explain how you understand that priorities? Why is > > something that always throws an exception in a very basic use-case > > only a "minor" problem? > > > (In case someone understands this wrong: I know that a higher priority > > doesn't necessarily mean that it will be fixed faster. I really just > > want to know how you get to this priority levels because they are > > clearly not like they are described in Jira.) > > -- > Fabio Maulo
