>>>>> On Wed, 22 Aug 2007 13:50:22 +0200, BOLLENGIER Eric said: > > On Wednesday 22 August 2007 13:22:13 Martin Simmons wrote: > > >>>>> On Wed, 22 Aug 2007 07:06:51 -0400, Dan Langille said: > > > > > > On 22 Aug 2007 at 10:35, BOLLENGIER Eric wrote: > > > > On Wednesday 22 August 2007 02:58:15 Dan Langille wrote: > > > > > On 21 Aug 2007 at 23:34, Eric Bollengier wrote: > > > > > > Hello, > > > > > > > > > > > > Yes, bacula is using PQescapeString which is an older, deprecated > > > > > > version of PQescapeStringConn. We have to use the new version to > > > > > > avoid this message, but it's not so easy at this time :) > > > > > > > > > > > > It's in my todo list. > > > > > > > > > > I'll do it. > > > > > > > > Ok, you have to modify the db_escape_string prototype > > > > to something like > > > > > > > > db_escape_string(B_DB *mdb, char *snew, char *old, int len) > > > > > > > > to be able to use mdb->db in PQescapeStringConn. > > > > > > I'll start this today. > > > > Can you make it automatically use PQescapeString if the version of > > PostgreSQL does not have PQescapeStringConn? > > > > > PQescapeString is appear in 7.2 and was deprecated in 7.3 > > I don't think it's a good idea to support postgresql before 7.3. > (postgresql 7.2 and previous are not supported by postgresql team)
The problem is that PQescapeStringConn is not available in all 7.3.x. __Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
