× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



John Earl wrote:

I'm writing an article on securing SQL and I'm looking for a really, really, long and complex SQL statement. Unfortunately my own SQl skills are kind of primitive, so I don't know how to generate this statement with the correct syntax.

John (who?):

Define 'statement' for "...a really, really, long and complex SQL statement."

That is, would you consider CREATE PROCEDURE...etc... to be a single 'statement'? The syntax diagram for SQL procs includes the "SQL-routine-body" portion which could be pretty complex (a compound-statement) and include lots of different 'statements'.

Or would it be statements separated by semi-colons such as might be generated via a SQL injection attack?

Or just statements where an UPDATE (or DELETE or INSERT) might be over a WHERE clause with sub-selects? Or even SELECTs with sub-selects? Or SELECTs under CTEs? SELECTs with table expressions?

So, has anyone got a copy of one that has multiple file names, multiple SELECT and UPDATE or DELETE statements, etc etc. The goal is not "un-readability", but rather complexity specifically as it relates to multiple tables and verbs in one statement.

Any and all assistance is greatly appreciated,

I could suggest a vendor contact for security advice, but maybe I can find something useful. I'll see what I can do for examples. Things are keeping me pretty busy though. <g>

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.