3 Answers
3

Just call it a statement. Then you can have an enumeration of statement types: OracleDMLStatement, OracleDDLStatement, and just OracleStatement. If it's an actual piece of PL/SQL you could have OraclePLSQLStatement, but without an example, it's hard to suggest much else.

You are not creating a DAO to access an oracle database. You are creating a DAO that accesses an Oracle database to solve a problem. Describe the probelem in the name of the DAO. For example, you might create a TpsReportReaderDAO to read TPS reports. Another example is, FlammyJammyHootyDAO might be used to apply Flammy Jammy to Hooty.

Summary: Use meaningful names; Oracle is the tool not the purpose. I don't use a Metal headed, wood handled tool to drive nails, I use a Hammer.

Actually, the goal is to create a generic DOA that wraps a nice OOP pattern we are using. This object abstract the database plumbing and will be used by our data tier.
–
Jordan ParmerFeb 17 '11 at 23:02