Hi!
Thanks a lot for this. I am not sure now if I will be able to use it. I am
afraid that if I do I will suddenly become its main supporter :)
I also still don't see how a connection can be reconnected at such a high
level. Even when I looked into the mySQL C api I didn't see anything that
Eric Frazier wrote:
I also still don't see how a connection can be reconnected at such a high
level.
It can't, unless your database specifically supports the command
reauthenticate. Oracle does, which is what he wrote this for, but I
don't think it's a standard part of SQL syntax so it will
On 2002-03-27, Eric Frazier [EMAIL PROTECTED] wrote:
If you have any idea where to find this code I would be thankful. I can
only find this..
[snip]
At 04:47 PM 3/26/02 -0500, John D Groenveld wrote:
Jeff Horn posted this a couple years ago either here or @ dbi-users
# Purpose: This
There are databases that allow you to change the current user without
reconnecting. In fact someone posted a module to do this a while back,
but I can't remember which database it was for. Seems like it was
Sybase or Informix.
Jeff Horn posted this a couple years ago either here or @
Hi,
If you have any idea where to find this code I would be thankful. I can only
find this..
http://aspn.activestate.com/ASPN/Mail/Message/perl-DBI/298774
Thanks,
Eric
At 04:47 PM 3/26/02 -0500, John D Groenveld wrote:
There are databases that allow you to change the current user without
On Sun, 24 Mar 2002, Andrew Ho wrote:
What would be ideal is if the database would allow you to change the
user on the current connection. I know PostgreSQL will allow this
using the command line interface psql tool (just do \connect
database user), but I'm not sure if you can do this using
Hi,
It might well be that in my particular case, I don't have anything to worry
about the connection time per each user most likely won't kill me or even
cause problems at first. But I am trying to build a system, and I don't want
to skip any reasonable efficences I can build in from the start.
Ed Grimm wrote:
First, I'll suggest that there are hopefully other areas you can look at
optimizing that will get you a bigger bang for your time - in my test
environment (old hardware), it takes 7.4 ms per
disconnect/reconnect/rebind and 4.8 ms per rebind. Admittedly, I'm
dealing with LDAP
On Fri, 2002-03-22 at 11:42, Andrew Ho wrote:
Hello,
EFI will have many different users, users as in database users. So am I
EFjust screwed and won't be able to keep connections open?
Do you mean users as in actual RDBMS level users? In other words, when you
say database users you mean
Hello,
CHWhat would be ideal is if the database would allow you to change the
CHuser on the current connection. I know PostgreSQL will allow this using
CHthe command line interface psql tool (just do \connect database
CHuser), but I'm not sure if you can do this using DBI.
CH
CHDoes anyone know
We encountered just this situation when we started to move from a win32
application connecting to an RDBMS to a web based app. On the win32
app, the DB authenticated each user with a loginid/pw. Since some users
still use the win32 app, we can't just abandon the DB authentication, so
here's
Hi,
I was all happy and rolling along when I read this in the docs.
With this limitation in mind, there are scenarios, where
the usage of Apache::DBI is depreciated. Think about a
heavy loaded Web-site where every user connects to the
database with a unique userid. Every
Hello,
EFI will have many different users, users as in database users. So am I
EFjust screwed and won't be able to keep connections open?
Do you mean users as in actual RDBMS level users? In other words, when you
say database users you mean different username/passwords used from, say,
a
13 matches
Mail list logo
