I wrote a similar CGI program at a recent client's site using Win32::ODBC. But the driver you use is not really relevent in my mind.
First off, if you are concerned about a user inputing complete SQL statements that will be destructive, either don't let them ( however this might involve creating an interface that allows column selection then crtieria, which can be a very complex solution) or REGEX the SQL for damaging code ( check for delete, and quanantine that user if they send such SQL ) and don't allow it to execute.
You can alway revoke permissions in the database to disallow a web user from writing to the database, by giving them select rights only. If the user isn't supposed to be able to write to the database this SHOULD be in place already. Check with your DBA.
If your system uses a login, then you can disallow this AND identify someone who attmepts to submit destructive code.
In reply to Re: Bad codes for SQL
by wardk
in thread Bad codes for SQL
by iic
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |