Re: 1 cset was pushed to core/stable: bug 4124 - unset dbconn property before ...
"Marc" <mfl-lg4R7s/[email protected]>
| Newsgroups | gmane.comp.cms.xaraya.bk-notices |
|---|---|
| Organization | Xaraya |
| Message-ID | <[email protected]> |
Good point. I'll correct that. "Jason Judge" <[email protected]> wrote in message news:[email protected]... > > "Marc" <[email protected]> wrote in message > news:[email protected]... > > So the open connection stops Postgres from saving a session var?? If > that's > > what's going on: nice catch! > > The openconnection call can probably be left out though, because a > > connection is opened just before the query is run. > > > > Marc > > Certain characters in the serialized connection object were causing > translation errors in the query. It still doesn't stop a similar problem > occuring elsewhere, such as strings in articles. > > I thought we had stopped putting database connection strings into the > database a long time ago, if only for the fact that the object contains the > database password, that would be stored within the database in cleartext. I > remember being told this was removed. Did it make its way back in again? > > -- JJ > >