Re^2: Abstracting SQL without Stored Procedures

[paulbort]

Using a hash is a good idea, regardless of how you store it, because it allows you to dynamically switch between statements, for things like different sort orders, or different inserts. ( My app inserts a row in either a queue table or a log table depending on outside data. By constructing the inserts to use the same parameter list, I can just use the appropriate hash key. )

Another way to store the statements would be with Data::Dumper.