Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Catering for postgres and mysql
08-27-2013, 07:37 PM, (This post was last modified: 08-27-2013, 07:39 PM by icedlava.)
#4
RE: Catering for postgres and mysql
Hmm now i look at the DB_escape_string() function I'm finding it a problem. It not only escapes the string but also applies htmlspecialchars to it. This is ok if we are outputting to HTML, but I think it is causing problems to store the string in the database already entity encoded.

Should we revise this? Do we need to separate out this functionality to have escaping for db storage, and second to prep for output to HTML?

Thanks.
Hi Phil,

(08-27-2013, 07:37 PM)phil Wrote: A few years ago we had full compatibility with postgres... we do have a ConnectDB_postgres.inc somewhere which has all the abstracted DB functions for postgres in .. there was no champion to maintain postgres and test it and I didn't wish to do it so we (I) let it go.

Yes, I can understand the work involved in trying to maintain for postgres and it's evolution as well as for mysql/mysqli. Perhaps we can look at it again when we have more time.

Thanks,
Reply


Messages In This Thread
Catering for postgres and mysql - by icedlava - 08-27-2013, 12:46 PM
RE: Catering for postgres and mysql - by icedlava - 08-27-2013, 06:49 PM
RE: Catering for postgres and mysql - by phil - 08-27-2013, 07:37 PM
RE: Catering for postgres and mysql - by icedlava - 08-27-2013, 07:37 PM
RE: Catering for postgres and mysql - by TurboPT - 08-28-2013, 12:33 PM
RE: Catering for postgres and mysql - by phil - 09-01-2013, 05:06 PM
RE: Catering for postgres and mysql - by TurboPT - 09-03-2013, 10:40 PM
RE: Catering for postgres and mysql - by tomglare - 09-03-2013, 10:49 PM
RE: Catering for postgres and mysql - by phil - 09-04-2013, 06:53 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)