databases.oracle generates incosistent names with Aliases
Bug #377312 reported by
Drew Smathers
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Storm |
New
|
Undecided
|
Unassigned |
Bug Description
databases.oracle module in oracle-support uses Aliases with default name derived for class variable counter on Alias. This causes different query to be generated for the same logical query which busts oracle's statement caching. This can (and has in my application) lead to ORA-04031 errors.
security vulnerability: | yes → no |
visibility: | private → public |
To post a comment you must log in.
If this is a problem for Oracle and doesn't negatively affect other databases, it'd probably be better to make the change to the database independent portion of Storm. What do you think?