|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #32977 Alternative pg_query_params returning query
Submitted: 2005-05-08 11:46 UTC Modified: 2012-03-31 05:28 UTC
From: direvus at gmail dot com Assigned:
Status: Wont fix Package: PostgreSQL related
PHP Version: 5.0.4 OS: Debian Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
46 - 26 = ?
Subscribe to this entry?

 [2005-05-08 11:46 UTC] direvus at gmail dot com
pg_query_params is a neat function, and I think it would be useful to have a separate function which resolves the statement (makes all the parameter substitutions) and then returns the completed SQL statement string, rather than immediately executing it and returning the result set.

You could, for example, have pg_resolve_params return the query string, and then have pg_query_params which essentially returns pg_query( pg_resolve_params( [...args...] ) );




Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2011-01-01 23:15 UTC]
-Package: Feature/Change Request +Package: PostgreSQL related
 [2012-03-31 05:28 UTC]
-Status: Open +Status: Wont fix
 [2012-03-31 05:28 UTC]
pg_query_params() relies on real prepared query feature in PostgreSQL.

Use new pg_escape_literal()/pg_escape_identifier() for escaping strings.
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Mon Jul 26 14:01:24 2021 UTC