Hello,
I am writing an application that is using DBI to access a MS SQL database
hosted on a remote server. I think I am having trouble with larger result
sets.
For example:
If I do
$stmt = SELECT * FROM tableA;
Where where tableA is around 10 rows, then my test script returns all of the
Hey!
You haven't mentioned which DBD you're using.
I suspect it's DBD::ODBC.
If so, you might want to check out this page:
http://search.cpan.org/~jurl/DBD-ODBC-1.13/ODBC.pm
for 'odbc_query_timeout' parameter.
Try playing with it, _however_, it should be unlimited by default.
Have you
I have been digging a bit to find what people consider loose ends in
Text::CSV_XS, and tried to summarize that (in no particular order) in
the new TODO list. Here TODO gives no guarantee that it will be done,
nor on any implementation or API that it might suggest, it is there now
just so I/we do
On Fri, 25 May 2007 15:22:02 -0400, Richard Dice [EMAIL PROTECTED]
wrote:
Merijn,
Why no Cc: to the list?
Thanks for asking, and for your work on this. (Looks like you just took
over maintainership recently...?)
Yes.
My recent I wish Text::CSV_XS could handle X... experience was -
On Fri, 25 May 2007, H.Merijn Brand wrote:
I have been digging a bit to find what people consider loose ends in
Text::CSV_XS, and tried to summarize that (in no particular order) in
the new TODO list. Here TODO gives no guarantee that it will be done,
nor on any implementation or API that it
H.Merijn Brand wrote:
Hi
=item Space delimited seperators
Discuss if and how CText::CSV_XS should/could support formats like
1 , foo , bar , 3.19 ,
If? Definitely. How? Errr...Is it so hard? When? Soon, so we can delete
specialized code written to deal with this. If you want to see the
