RE: "connect" not connecting

DBI->trace(...) might help. You should also review the docs on the use of errstr. You should be using $DBI::errstr, not DBI->errstr to the best of my knowledge and according to the docs. Eric D. Berg IPRS Infrastructure From: dbenti...@gmail.com [mailto:dbenti...@gmail.com] On Behalf Of Dan B

RE: Perl for Banking and Finance Domain

All kinds of stuff. Data loading (we regularly load market data, for example, on the order of millions of rows daily, web-based tools, sysadmin scripts, reportingyou name it and Perl is there in finance. There are some who even run it on Windows. ructure > -Original Message- > F

RE: DBD ODBC

Jason, the way ODBC works on Linux is that there is a layer of abstraction which is the odbc manager. You're probably using unixodbc, or should be. The install of unixodbc will contain a program that DBD::ODBC (and others) will use to get configuration information that it uses to build DBD::OD

RE: any issues with $DBI::err not getting cleared on a ->connect call?

I believe that this is pretty clear in the DBI man page. Just remember that if you have a connection problem, you won't have a db handle (i.e., $dbh) so you should use $DBI::errstr as per the docs: "connect" $dbh = DBI->connect($data_source, $username, $password)

RE: DBD::Sybase and DBI->get_info()

Thanks, Michael. Turns out that $dbh->{syb_oc_version} does what I've been looking for for quite some time. For native Sybase libs I get: Sybase Client-Library/12.5.1/P-EBF14755 ESD #19/DRV.12.5.1.9/Linux x86_64/Linux 2.4.21-47.0.1.ELsmp x86_64/BUILD1251-050/OPT/Mon Jun 25 01:02:06 2007 For F

RE: DBD::Sybase and DBI->get_info()

Thanks, John. If anyone can comment with authority on the lack of intraspection capabilities in DBD::Sybase, that'd be helpful. I looked through the code as well, and didn't find anything to say one way or another. Get_info() appears to be relatively new to DBI, and it look slike there is som

RE: Assigning private attributes to DBI database handles

Perfect, Martin. That's just what I needed. I spent an hour or so looking for this, because I knew it was there somewhere. Must have read everything up to that one in the DBI docs. Thanks again. > -Original Message- > From: Martin J. Evans [mailto:martin.ev...@easysoft.com] > Sent: F

RE: DBD::ODBC Segfaults on SET TEXTSIZE and TRUNCATE TABLE

Yes! Thanks for the clarification, Martin. Folks, I've had an opportunity to work with Martin and a few others on the EasySoft team on this and a few other problems, and I want you to know that they've been really helpful. As a long-time OSS guy, I'm highly suspicious of proprietary software a

Assigning private attributes to DBI database handles

I'd like to set some private attributes on my db handles so that later I can interrogate them to get that information. We are doing this with statement handles, but not DB handles, and it simply doesn't seem to be working in any case. Any thoughts? Eric ___

DBD::Sybase and DBI->get_info()

As we migrate our codebase from Sybase (DBD::Sybase) to MS SQL (DBD::ODBC), it would be helpful to have low-level info about the drivers available, and it seems that the DBI->get_info() method is the place to go for that. It is supported adequately in DBD::ODBC, but it appears that DBD::Sybase

RE: What's the relationship between LongReadLen and TEXTSIZE?

Hey, Martin. TEXTSIZE is a server-side variable that determines the data length returned by a SELECT statement. It appears to be roughly the server-side equivalent of LongReadLen, where LongReadLen (per your notes below) is a driver setting that determines at what size buffer will be allocated

RE: What's the relationship between LongReadLen and TEXTSIZE?

Omg...it's bad enough that we have to use a MS SQL server...but running our code on Windows...thankfully, that's not a problem we have. Thanks for the suggestion though, John. As far as my research has gone so far, it appears at this point that the TEXTSIZE setting is a server-side setting, wh

What's the relationship between LongReadLen and TEXTSIZE?

I'm setting up to use DBD::ODBC with the FreeTDS driver to go against a MS SQL server and am hoping to nail down the specifics of the relationship between setting $dbh->{LongReadLen} and TEXTSIZE. So far, LongReadLen has had exactly no impact on retrieval of long data from my MS sql server. Re

RE: DBD::ODBC Segfaults on SET TEXTSIZE and TRUNCATE TABLE

Just a quick update: We switched back to using the FreeTDS driver under DBD::ODBC with the unixODBC ODBC manager on Linux and the segfault problem went away. That seems to suggest to me that it's a problem with the Easysoft driver, and I've communicated this to the Easysoft team. BTW, the Easy

RE: DBD::ODBC Segfaults on SET TEXTSIZE and TRUNCATE TABLE

Thanks, Martin. I've been working with Richard on this for a few days and he's been very helpful. Just not sure what's up here yet, but it was recommended that I upgrade from the 1.3 version that we've got packaged for use here at the bank to 1.4. We'll see if that makes a difference. Many

DBD::ODBC Segfaults on SET TEXTSIZE and TRUNCATE TABLE

Posted this in the Google Group, but not sure if it's going through, so I apologize for the duplicate if that's the case. We're continuing with our struggles to get Perl working properly to connect to MS SQL server, and have come up against a nasty bug that results in segmentation faults when a