>
> One thing to be careful is if you are relying on 'transactions' to handle
> anything. Obviously the transaction has to be in the same connection just to
> work. Despite what others have said, the PDO connection will be different to
> the generic mysql connection as it is a separate process
>
> As long as you test it (hopefully using some sort of automated tests) you
> should be right.
>
> Since you're using persistent connections (make sure you set pdo to do the
> same), I don't think you're really doubling the number of connections.
Yeah, I think PDO uses the underlying mysql/
Hi,
If the databases are in the same mysql server, then you could qualify
the table select with the database name and simply re-use the
connection
select db_name.table_name.field from db_name.table_name [where]
No offence, but if I saw this in an application's source code, I'd run
a mile.
ser. What have I missed?
Thanks,
Stan
""Andy Shellam (Mailing Lists)"" wrote in
message news:fd8200b0-e18a-4afd-8ffc-f51080621...@networkmail.eu...
Hi,
I got around this by creating a database wrapper class which gets
passed the credentials from the app's config file.
Hi,
I got around this by creating a database wrapper class which gets
passed the credentials from the app's config file. An instance of the
class is created and saved in the session, and every query to the
database runs through the class's Query() wrapper method which checks
if the conne
-Remote Server
"old_passwords" "ON"
"version" "5.0.45"
That's probably why - as I said in my previous e-mail, the mysqlng
driver doesn't support the old authentication mechanism. If you
cannot change the remote server, you need to re-compile PHP with the
MySQL client library (libmysql)
The mysqlnd driver doesn't support MySQL 4.1 or earlier - it looks
like the server that you think is 5.0.45 is actually a lot older, or
your user account on MySQL has been set up using the old
authentication method.
The solution would be to re-compile PHP 5.3 with the original MySQL
clien
orted
any more and I should be using pg_execute instead... Thanks again.
Giff
On Tue, 2009-10-27 at 19:51 +0000, Andy Shellam (Mailing Lists) wrote:
Hi Giff,
No worries - I know the feeling well!
At first glance this looks OK, however I notice that there is no
"res"
property defi
Hi Chris,
$this->res = @pg_execute($this->session, $query);
PHP is therefore trying to assign a query result to a property that
doesn't exist. I would have expected PHP to throw an error at this
but it may have been obscured with your logging settings, I'm not
sure.
Close - the '@' bef
y
On 27 October2009, at 19:36, Giff Hammar wrote:
Andy,
Sometimes I'm too fast for my own good. I added .txt to the file and
it
should be visible as http://www.sv-phoenix.com/dbi_pgsql.txt. Just
appending the .txt didn't work.
Thanks for taking a look!
Giff
On Tue, 2009-10-27 at
Hi Giff,
I want to have a look at this for you, but you'll need to put the file
on your server as plain-text because your server is parsing the PHP
code and only sending us the output, not the source code.
Append *.txt to your file on the server and we should be able to see
it better!
A
11 matches
Mail list logo