I have been doing more with SQL lately, and I have lots of SQL code to run from Perl using DBI. There is so much of it that lately I prefer to have the SQL code in a separate file from my Perl, because the vim editor highlights the SQL and Perl syntax correctly, based on the filename. However, I think this makes a module that uses the SQL file harder to deploy, because the Perl code has to find the SQL file based on where it was installed by the module.
I can think of several approaches to fixing this. One would be to fix my editor so that all 'here docs' are interpreted as SQL, or to learn some new trick about paths and module installation. Or likely there is an even a better approach that I haven't thought of.
Suggestions, perl lang vimrc patches, perl module tricks all welcome! Thanks.
It should work perfectly the first time! - toma