databases.oracle generates incosistent names with Aliases

Bug #377312 reported by Drew Smathers on 2009-05-16
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Storm
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.

Drew Smathers (djfroofy) on 2009-05-16
security vulnerability: yes → no
visibility: private → public
James Henstridge (jamesh) wrote :

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?

Drew Smathers (djfroofy) wrote :

Yes, I agree. Sorry, but I forgot to add link to my patch in bug report:

http://bazaar.launchpad.net/~djfroofy/storm/oracle-support-patches/revision/278

The change indeed is made to storm.databases.oracle since the issue is specific to how oracle-specific code uses Aliases.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers