Thanks. I’ve had a look. This is pretty much what I did except it handles it
in SearchBuilder::Handle which is the right thing to do. However you probably
don’t want to have to go through this every time someone wants to set a new
attribute on the DSN for some database driver or other. It’s already been done
once for Oracle’s sid=, now for mysql_sock=, what next, PostgreSQL options=?
So why not have a general purpose --db-dsn-attrs= switch and
$RT::DatabaseDSNAttrs string which is just a semi-colon delimited string of
attribute settings that is tacked onto the DSN?
Ian Grant, Computer Lab., William Gates Building, JJ Thomson Ave., Cambridge
Phone: +44 1223 334420
I’m using RT 3.0.0 with MySQL with the socket /local/own-1/rt/mysql.sock and
’make initialize-database’ is failing because the driver expects the socket to
be in /tmp I want to specify a mysql_socket option in the DSN. What is the
easiest way to achieve this, I wonder?
Ian
Ian Grant, Computer Lab., William Gates Building, JJ Thomson Ave., Cambridge
Phone: +44 1223 334420
IIRC, there’s a patch sitting in the rt3 bugs queue that didn’t make it
in before RT 3.0.0. But you can login to rt.3.fsck.com as guest/guest
and give it a shot. If the patch works cleanly for you, That would
definitely help get it into the core release.On Wed, Apr 02, 2003 at 04:49:27PM +0100, Ian Grant wrote:
I’m using RT 3.0.0 with MySQL with the socket /local/own-1/rt/mysql.sock and
‘make initialize-database’ is failing because the driver expects the socket to
be in /tmp I want to specify a mysql_socket option in the DSN. What is the
easiest way to achieve this, I wonder?
Ian
Ian Grant, Computer Lab., William Gates Building, JJ Thomson Ave., Cambridge
Phone: +44 1223 334420
IG> I’m using RT 3.0.0 with MySQL with the socket /local/own-1/rt/mysql.sock and
IG> ‘make initialize-database’ is failing because the driver expects the socket to
IG> be in /tmp I want to specify a mysql_socket option in the DSN. What is the
IG> easiest way to achieve this, I wonder?
The easiest way is to specify the alternate socket when building
mysql, so that the alternate path is hard-coded into the client libs.
that’s what I used to do…
i suppose you could specify it in the my.cnf or perhaps an environment
variable. dunno about those, though.
IG> I’m using RT 3.0.0 with MySQL with the socket /local/own-1/rt/mysql.sock and
IG> ‘make initialize-database’ is failing because the driver expects the socket to
IG> be in /tmp I want to specify a mysql_socket option in the DSN. What is the
IG> easiest way to achieve this, I wonder?
The easiest way is to specify the alternate socket when building
mysql, so that the alternate path is hard-coded into the client libs.
that’s what I used to do…
i suppose you could specify it in the my.cnf or perhaps an environment
variable. dunno about those, though.
I ran into this one too - a symlink did the trick for me, as a quick
lashup job.
IG> I’m using RT 3.0.0 with MySQL with the socket /local/own-1/rt/mysql.sock and
IG> ‘make initialize-database’ is failing because the driver expects the socket to
IG> be in /tmp I want to specify a mysql_socket option in the DSN. What is the
IG> easiest way to achieve this, I wonder?
The easiest way is to specify the alternate socket when building
mysql, so that the alternate path is hard-coded into the client libs.
that’s what I used to do…
i suppose you could specify it in the my.cnf or perhaps an environment
variable. dunno about those, though.