db-api docs: invalid REGEX SQL equiv for SQLite

It's not entirely clear to me what the problem is you're pointing out here. Given that we don't want to remove the line, could you suggest an alternative formulation (it's a balance between acknowledging that SQLite actually uses Python to do some of the heavy lifting here, without bogging the documentation down in relatively minor details at this point). Any suggestions on what we could do to make it clearer?

It doesn't seem to me correct or useful to list a SQLite SQL equivalent if there isn't one.

If you're going to leave it, my suggestion would be to move the line

"In the case of SQLite, which doesn’t natively support regular-expression lookups, the syntax is that of Python’s re module."

to directly below the code block of SQL equivs. This would put the two lines closer together, reducing the chance that someone would see the SQLite example without the accompanying/qualifying note (especially as a similar equiv appears in IREGEX, relying on this note for clarification)

Perhaps format it as a note? Add an asterisk after the -- SQLite?

Fix minor nit with SQLite regexp documentation

I would suggest that the structure of the documentation be left as it is, and the offending sentence be changed. I have attached a patch for db-api.txt (see 6047.diff).

Hopefully this will explain why the SQL looks like it does (since it is indeed the SQL that is sent to the SQLite engine in the case given).

Those seeking light relief may wish to consult http://holdenweb.blogspot.com/2008/04/for-want-of-nail.html concerning the history of the associated patch.

update patch to apply to trunk

(In [11541]) Fixed #6047 -- Minor correction to the documentation regarding regex field lookups. Thanks to Richard D. Worth for the suggestion, and Steve Holden for the text.