https://bz.apache.org/bugzilla/show_bug.cgi?id=60440
Christopher Head <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #4 from Christopher Head <[email protected]> --- Nope, that syntax doesn’t work either: Internal error (specific information not available): AH00632: failed to prepare SQL statements: ERROR: column "$1" does not exist\nLINE 1: PREPARE myMap (varchar) AS SELECT "$1"\n ^\n I understand that this limitation comes from PostgreSQL. The thing is, from the Apache documentation, I had no idea that PostgreSQL would ever even *see* the map name! From looking at the mod_rewrite documentation, it’s written as if the rewrite map name is purely a private identifier used by Apache itself. Documenting the specific requirements for rewrite map names for each database is definitely silly, I agree. Documenting that the rewrite map name *will be used as a database identifier*, and therefore must obey the DBMS-specific rules of same, and to please look at your DBMS for details, IMO makes perfect sense, and is something I would never have guessed just from looking at the mod_rewrite documentation today. I’ve reopened this ticket with that idea in mind, but if you don’t want to edit accordingly, you can close again. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
