Re: DBD::mysql 4.004 Released!

2007-03-26 Thread Scott T. Hildreth
Pat, The #ifdef's still need to be removed in the calls below. Thanks. dbdimp.c: In function `mysql_st_fetch': dbdimp.c:3429: error: too few arguments to function `mysql_dr_error' dbdimp.c:3593: error: too few arguments to function `mysql_dr_error' dbdimp.c: In function

DBD::Sybase and extended sysprocesses columns

2007-03-26 Thread Matthew Persico
In Sybase 12.5 (don't know about earlier versions) there are three columns in sysprocesses: clientname varchar 30 NULL NULL 1 NULL NULL NULL 0 clienthostname varchar 30 NULL NULL 1 NULL NULL NULL 0 clientapplname varchar 30 NULL NULL 1 NULL NULL

Re: DBD::Sybase and extended sysprocesses columns

2007-03-26 Thread Michael Peppler
Matthew Persico wrote: In Sybase 12.5 (don't know about earlier versions) there are three columns in sysprocesses: clientname varchar 30 NULL NULL 1 NULL NULL NULL 0 clienthostname varchar 30 NULL NULL 1 NULL NULL NULL 0 clientapplname varchar 30 NULL

Re: DBD::Sybase and extended sysprocesses columns

2007-03-26 Thread Matthew Persico
On 3/26/07, Jason L. Froebe [EMAIL PROTECTED] wrote: These are set at the ASE server not at the client connection ct_connect() (v12.0 and higher). So.. it would be nice for Michael to add them as part of the standard 'after connect' processing but we do have a workaround until then. :)

Re: DBD::Sybase and extended sysprocesses columns

2007-03-26 Thread Jason L. Froebe
--- Matthew Persico [EMAIL PROTECTED] wrote: In Sybase 12.5 (don't know about earlier versions) there are three columns in sysprocesses: clientname varchar 30 NULL NULL 1 NULL NULL NULL 0 clienthostname varchar 30 NULL NULL 1 NULL NULL NULL 0