Date: 08/09/00
- Next message: Manuel Lemos: "[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.0.2 Release date"
- Previous message: Hartmut Holzgraefe ( <email protected>): "Re: [PHP-DEV] duplicate entries, even worse ..."
- Next in thread: Manuel Lemos: "[PHP-DEV] Re: PHP 4.0 Bug #6033 Updated: Can't open more than one non-persistent connections to the same database"
- Maybe reply: Manuel Lemos: "[PHP-DEV] Re: PHP 4.0 Bug #6033 Updated: Can't open more than one non-persistent connections to the same database"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello Bug,
On 10-Aug-00 05:00:00, you wrote:
>ID: 6033
>Updated by: danny
>Reported By: mlemos <email protected>
>Status: Feedback
>Bug Type: Informix related
>Assigned To: danny
>Comments:
>One solution is not to use shared memory connections
>(ipcshm) but streams pipes (ipcstr) if you have them,
>or tcp/ip (tlitcp or soctcp). It is the recommended way.
>Despite what the manual says, ipcshm is not always faster,
>it depends on the OS.
For some reason I am only able to install and start the Informix server
with shared memory. Maybe it's a configuration problem that I am not able
to sort. Often Informix error messages are too cryptic to be useful.
>Even if you use shared memory connections you can
>access as many different databases as you like with
>the database:table syntax using one single connection.
>You can even have transactions involving different databases
>this way. It is certainly more efficient.
That is not viable for me because I am developing a Informix driver for
Metabase PHP database abstraction package and what you suggest would
require me parse and change user queries.
Anyway, that is not the worst problem. The worst problem is having to
connect to the same server as a different user. I need that when the
Metabase manager class installs a new database. First it needs to create
the database as DBA user and then it needs to install the schema objects as
normal user.
What I suggest is that you either effectively close Informix non-persistent
connections ifx_Close which is the most expected behaviour and eventually
add a new option to php.ini to let users deliberately ask to not close such
connections before the end of the script if they really want to.
Regards,
Manuel Lemos
Web Programming Components using PHP Classes.
Look at: email protected>?subject=Re:%20[PHP-DEV]%20Re:%20PHP%204.0%20Bug%20#6033%20Updated:%20Can't%20open%20more%20than%20one%20non-persistent%20connections%20to%20the%20same%20database&replyto=1947.256T49T14373282mlemos <email protected>">mlemos <email protected>">http://phpclasses.UpperDesign.com/?user=mlemos <email protected>
-- E-mail: mlemos <email protected> URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp ---- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Manuel Lemos: "[PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] 4.0.2 Release date"
- Previous message: Hartmut Holzgraefe ( <email protected>): "Re: [PHP-DEV] duplicate entries, even worse ..."
- Next in thread: Manuel Lemos: "[PHP-DEV] Re: PHP 4.0 Bug #6033 Updated: Can't open more than one non-persistent connections to the same database"
- Maybe reply: Manuel Lemos: "[PHP-DEV] Re: PHP 4.0 Bug #6033 Updated: Can't open more than one non-persistent connections to the same database"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

