ANNOUNCE: DBD::ADO 2.78
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.78.tar.gz size: 45044 bytes md5: cf0559199ee51e261d9ccb0d1ca9771a Changes: Modified t/09bind.t to use Test::More. Added data_sources(). Moved some datatype related stuff into DBD::ADO::TypeInfo. Win32::OLE::Const is no longer being used (in favor of DBD::ADO::Const). Steffen
nmaking dbd-mysql errors
Hi: Please see snippet below. Perhaps someone could advise me where to go from here? OS is Win2K Thanks in advance, Howard Begin snippet+++ C:\Documents and Settings\Administrator\Desktop\Downloads\DBD-mysql-2.9003>nmake Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved. cp lib/DBD/mysql.pm blib\lib\DBD/mysql.pm cp lib/DBD/mysql/GetInfo.pm blib\lib\DBD/mysql/GetInfo.pm cp lib/Mysql.pm blib\lib\Mysql.pm cp lib/DBD/mysql/INSTALL.pod blib\lib\DBD/mysql/INSTALL.pod cp lib/Mysql/Statement.pm blib\lib\Mysql/Statement.pm cp lib/Bundle/DBD/mysql.pm blib\lib\Bundle/DBD/mysql.pm cl -c -ID:/Perl/site/lib/auto/DBI -IC:\mysql\include -nologo -Gf -W3 - MD -DNDEBUG -O1 -DWIN32 -D_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT -DPERL_IMPL ICIT _CONTEXT -DPERL_IMPLICIT_SYS -DUSE_PERLIO -DPERL_MSVCRT_READFIX -MD -DNDEBUG -O1 -DVERSION=\"2.9003\" -DXS_VERSION=\"2.9003\" "-ID:\Perl\lib\CORE" dbdimp .c 'cl' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x1' Stop. End snippet+++ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.537 / Virus Database: 332 - Release Date: 06/11/2003
DBI Proxy Server Instability on Win with SQL Server
Ive been searching and using mailing lists to try to find the best way to access, in multi-threaded mode, a SQL Server Database running on Windows 2000 from Linux perl scripts. Im hearing that there seems to be inherent instability when running threads or forks, with the below note summarizing the issue (from someone on a mail group). Is there any way to have a stable environment doing what Im trying to do? Yes, Dave, I used 5.8 AS binaries with built-in ithreads. i believe your proxy hang is one symptom of thread unsafety. look at Net::Daemon when --childs=5. Jochen "forks" five children, but forks are threads on windows, so we have five threads listening simultaneously on the same port on the same select statement; then one of them starts heading toward the accept(), but its only a thread, so another thread starts and beats it to the accept(), so now some threads are waiting on select, others on accept, yada yada... ??? hanging, crashing, Storable croaks, are but some of the colorful symptoms. :-) Thanks, David Wesner President DataSwitch Information Services, Inc. Phone: (574) 546-2084 Fax: (574) 546-3105 Email: [EMAIL PROTECTED] Web: www.dataswitch.com
Re: DBD::ORACLE Hanges
Already fixed for the next release. Tim. On Fri, Nov 07, 2003 at 03:23:27PM +0100, Waldemar ?urowski wrote: > W li?cie z pi?, 07-11-2003, godz. 14:23, Tim Bunce pisze: > > And if so: http://www.mail-archive.com/[EMAIL PROTECTED]/msg18192.html > > Thank You Tim, that would be my next advise :) as the symptoms(?) are > exactly the same. > > Anyway - perhaps You need a little bit safer way to detect your > developing environment? > > Waldemar > >
Stored procedures and DBD::Sybase
Hello,
I am using DBI v. 1.38, DBD::Sybase v. 1.01 (?), and FreeTDS 0.61.2 to
connect to an MSSQL 6.5 database from a Linux client and I am having
problems retrieving the values of out parameters to a stored procedure
call.
I followed the example in the DBD::Sybase docs modifying for my purpose
as follows:
#!/usr/bin/perl
use DBI;
use DBD::Sybase;
my $dbh = DBI->connect('dbi:Sybase:server=',
'sa', '', {PrintError => 1, AutoCommit => 1});
$dbh->do('use tempdb');
my $sql = q{
declare @a int
declare @b varchar(10)
exec foo @a output, @b output
declare @c varchar(255)
select @c = @b + ' : ' + convert(varchar(3), @a)
print @c
};
my $sth = $dbh->prepare($sql);
$sth->execute;
do {
while ($d = $sth->fetch) {
$rt = $sth->{'syb_result_type'};
print("Iterating: $rt\n");
if ($rt == DBD::Sybase::CS_PARAM_RESULT) {
print("found param result [EMAIL PROTECTED]");
$a = $$d[0];
$b = $$d[1];
} elsif ($rt == DBD::Sybase::CS_ROW_RESULT) {
print("found row result [EMAIL PROTECTED]");
} elsif ($rt == DBD::Sybase::CS_STATUS_RESULT) {
print("found status result [EMAIL PROTECTED]");
}
}
} while($sth->{'syb_more_results'});
print("Retrieved values $a $b\n");
And received the following output:
Iterating: 4043
found status result [0]
hello : 5
Retrieved values
As I understand the docs, the there should have been a CS_PARAM_RESULT
result set but there was not. As you see, I even printed out the
results from the sql to make sure the out params were being set. Am I
doing something wrong or is this a known limitation when using my
configuration. Perhaps I can use the Sybase Open Client libraries
instead?
I help will be greatly appreciated.
Thank you,
Steven
Re: nmaking dbd-mysql errors
Looks like you are missing the c compiler that your make file is requesting/requiring. Chuck [EMAIL PROTECTED] wrote: Hi: Please see snippet below. Perhaps someone could advise me where to go from here? OS is Win2K Thanks in advance, Howard Begin snippet+++ C:\Documents and Settings\Administrator\Desktop\Downloads\DBD-mysql-2.9003>nmake Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved. cp lib/DBD/mysql.pm blib\lib\DBD/mysql.pm cp lib/DBD/mysql/GetInfo.pm blib\lib\DBD/mysql/GetInfo.pm cp lib/Mysql.pm blib\lib\Mysql.pm cp lib/DBD/mysql/INSTALL.pod blib\lib\DBD/mysql/INSTALL.pod cp lib/Mysql/Statement.pm blib\lib\Mysql/Statement.pm cp lib/Bundle/DBD/mysql.pm blib\lib\Bundle/DBD/mysql.pm cl -c -ID:/Perl/site/lib/auto/DBI -IC:\mysql\include -nologo -Gf -W3 - MD -DNDEBUG -O1 -DWIN32 -D_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT -DPERL_IMPL ICIT _CONTEXT -DPERL_IMPLICIT_SYS -DUSE_PERLIO -DPERL_MSVCRT_READFIX -MD -DNDEBUG -O1 -DVERSION=\"2.9003\" -DXS_VERSION=\"2.9003\" "-ID:\Perl\lib\CORE" dbdimp .c 'cl' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x1' Stop. End snippet+++ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.537 / Virus Database: 332 - Release Date: 06/11/2003
Re: Stored procedures and DBD::Sybase
Steven,
I believe that you are misunderstanding what it is that you are
receiving. The only output from your commands is the print @c. This
comes through the error handler since a print statement is a level 0 or
level 10 message from the server and not a result set. Try changing the
print to a select and then you can receive it as a row result.
Regards,
Chuck
[EMAIL PROTECTED] wrote:
Hello,
I am using DBI v. 1.38, DBD::Sybase v. 1.01 (?), and FreeTDS 0.61.2 to
connect to an MSSQL 6.5 database from a Linux client and I am having
problems retrieving the values of out parameters to a stored procedure
call.
I followed the example in the DBD::Sybase docs modifying for my purpose
as follows:
#!/usr/bin/perl
use DBI;
use DBD::Sybase;
my $dbh = DBI->connect('dbi:Sybase:server=',
'sa', '', {PrintError => 1, AutoCommit => 1});
$dbh->do('use tempdb');
my $sql = q{
declare @a int
declare @b varchar(10)
exec foo @a output, @b output
declare @c varchar(255)
select @c = @b + ' : ' + convert(varchar(3), @a)
print @c
};
my $sth = $dbh->prepare($sql);
$sth->execute;
do {
while ($d = $sth->fetch) {
$rt = $sth->{'syb_result_type'};
print("Iterating: $rt\n");
if ($rt == DBD::Sybase::CS_PARAM_RESULT) {
print("found param result [EMAIL PROTECTED]");
$a = $$d[0];
$b = $$d[1];
} elsif ($rt == DBD::Sybase::CS_ROW_RESULT) {
print("found row result [EMAIL PROTECTED]");
} elsif ($rt == DBD::Sybase::CS_STATUS_RESULT) {
print("found status result [EMAIL PROTECTED]");
}
}
} while($sth->{'syb_more_results'});
print("Retrieved values $a $b\n");
And received the following output:
Iterating: 4043
found status result [0]
hello : 5
Retrieved values
As I understand the docs, the there should have been a CS_PARAM_RESULT
result set but there was not. As you see, I even printed out the
results from the sql to make sure the out params were being set. Am I
doing something wrong or is this a known limitation when using my
configuration. Perhaps I can use the Sybase Open Client libraries
instead?
I help will be greatly appreciated.
Thank you,
Steven
Re: nmaking dbd-mysql errors
Chuck Fox said: > Looks like you are missing the c compiler that your make file is > requesting/requiring. > >>'cl' is not recognized as an internal or external command, >>operable program or batch file. Yes, cl.exe is the C/C++ compiler that comes with Visual Studio. Colin -- Colin W. Wetherbee http://hydrogen.denterprises.org/
RE: Stored procedures and DBD::Sybase
Chuck,
Thanks for the response. Although, the DBD::Sybase docs do detail
retrieving sproc out params as I have done, using the select statement
to explicitly form a result is an interesting solution.
One additional question rises from the fact that DBD::Sybase can handle
returning many result sets and my real life procedure (not this test
one) actually does return many result sets. With this solution the only
way I can know that I am getting my procedure params is by placing my
select statement last and assuming that the last result row is the one I
am interested in. Is there a better way of doing this? Also, can I move
the client-side cursor to the end of the result set without having to
fetch all the intermediate results?
Thank you greatly,
Steven
-Original Message-
From: Chuck Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 12:51 PM
To: Steven Velez
Cc: [EMAIL PROTECTED]
Subject: Re: Stored procedures and DBD::Sybase
Steven,
I believe that you are misunderstanding what it is that you are
receiving. The only output from your commands is the print @c. This
comes through the error handler since a print statement is a level 0 or
level 10 message from the server and not a result set. Try changing the
print to a select and then you can receive it as a row result.
Regards,
Chuck
[EMAIL PROTECTED] wrote:
>Hello,
>
>I am using DBI v. 1.38, DBD::Sybase v. 1.01 (?), and FreeTDS 0.61.2 to
>connect to an MSSQL 6.5 database from a Linux client and I am having
>problems retrieving the values of out parameters to a stored procedure
>call.
>
>I followed the example in the DBD::Sybase docs modifying for my purpose
>as follows:
>
>#!/usr/bin/perl
>
>use DBI;
>use DBD::Sybase;
>
>my $dbh = DBI->connect('dbi:Sybase:server=',
>'sa', '', {PrintError => 1, AutoCommit => 1});
>
>$dbh->do('use tempdb');
>my $sql = q{
>declare @a int
>declare @b varchar(10)
>exec foo @a output, @b output
>declare @c varchar(255)
>select @c = @b + ' : ' + convert(varchar(3), @a)
>print @c
>};
>
>my $sth = $dbh->prepare($sql);
>$sth->execute;
>do {
>while ($d = $sth->fetch) {
>$rt = $sth->{'syb_result_type'};
>print("Iterating: $rt\n");
>if ($rt == DBD::Sybase::CS_PARAM_RESULT) {
>print("found param result [EMAIL PROTECTED]");
>$a = $$d[0];
>$b = $$d[1];
>} elsif ($rt == DBD::Sybase::CS_ROW_RESULT) {
>print("found row result [EMAIL PROTECTED]");
>} elsif ($rt == DBD::Sybase::CS_STATUS_RESULT) {
>print("found status result [EMAIL PROTECTED]");
>}
>}
>} while($sth->{'syb_more_results'});
>print("Retrieved values $a $b\n");
>
>
>And received the following output:
>
>Iterating: 4043
>found status result [0]
>hello : 5
>Retrieved values
>
>
>As I understand the docs, the there should have been a CS_PARAM_RESULT
>result set but there was not. As you see, I even printed out the
>results from the sql to make sure the out params were being set. Am I
>doing something wrong or is this a known limitation when using my
>configuration. Perhaps I can use the Sybase Open Client libraries
>instead?
>
>I help will be greatly appreciated.
>
>Thank you,
>Steven
>
>
Re: Stored procedures and DBD::Sybase
Steven,
Do perldoc DBD::Sybase. There is a writeup on how to detect multiple
result sets. This method deviates from the DBI standards. Basically,
you check a special Sybase attribute in the statement handle,
syb_more_results, to see if more fetchable results exist.
Chuck
[EMAIL PROTECTED] wrote:
Chuck,
Thanks for the response. Although, the DBD::Sybase docs do detail
retrieving sproc out params as I have done, using the select statement
to explicitly form a result is an interesting solution.
One additional question rises from the fact that DBD::Sybase can handle
returning many result sets and my real life procedure (not this test
one) actually does return many result sets. With this solution the only
way I can know that I am getting my procedure params is by placing my
select statement last and assuming that the last result row is the one I
am interested in. Is there a better way of doing this? Also, can I move
the client-side cursor to the end of the result set without having to
fetch all the intermediate results?
Thank you greatly,
Steven
-Original Message-
From: Chuck Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 12:51 PM
To: Steven Velez
Cc: [EMAIL PROTECTED]
Subject: Re: Stored procedures and DBD::Sybase
Steven,
I believe that you are misunderstanding what it is that you are
receiving. The only output from your commands is the print @c. This
comes through the error handler since a print statement is a level 0 or
level 10 message from the server and not a result set. Try changing the
print to a select and then you can receive it as a row result.
Regards,
Chuck
[EMAIL PROTECTED] wrote:
Hello,
I am using DBI v. 1.38, DBD::Sybase v. 1.01 (?), and FreeTDS 0.61.2 to
connect to an MSSQL 6.5 database from a Linux client and I am having
problems retrieving the values of out parameters to a stored procedure
call.
I followed the example in the DBD::Sybase docs modifying for my purpose
as follows:
#!/usr/bin/perl
use DBI;
use DBD::Sybase;
my $dbh = DBI->connect('dbi:Sybase:server=',
'sa', '', {PrintError => 1, AutoCommit => 1});
$dbh->do('use tempdb');
my $sql = q{
declare @a int
declare @b varchar(10)
exec foo @a output, @b output
declare @c varchar(255)
select @c = @b + ' : ' + convert(varchar(3), @a)
print @c
};
my $sth = $dbh->prepare($sql);
$sth->execute;
do {
while ($d = $sth->fetch) {
$rt = $sth->{'syb_result_type'};
print("Iterating: $rt\n");
if ($rt == DBD::Sybase::CS_PARAM_RESULT) {
print("found param result [EMAIL PROTECTED]");
$a = $$d[0];
$b = $$d[1];
} elsif ($rt == DBD::Sybase::CS_ROW_RESULT) {
print("found row result [EMAIL PROTECTED]");
} elsif ($rt == DBD::Sybase::CS_STATUS_RESULT) {
print("found status result [EMAIL PROTECTED]");
}
}
} while($sth->{'syb_more_results'});
print("Retrieved values $a $b\n");
And received the following output:
Iterating: 4043
found status result [0]
hello : 5
Retrieved values
As I understand the docs, the there should have been a CS_PARAM_RESULT
result set but there was not. As you see, I even printed out the
results from the sql to make sure the out params were being set. Am I
doing something wrong or is this a known limitation when using my
configuration. Perhaps I can use the Sybase Open Client libraries
instead?
I help will be greatly appreciated.
Thank you,
Steven
DBI::Shell producing errors during test on RedHat 9
cpan> install DBI::Shell Running install for module DBI::Shell Running make for T/TL/TLOWERY/DBI-Shell-11.93.tar.gz Is already unwrapped into directory /root/.cpan/build/DBI-Shell-11.93 CPAN.pm: Going to build T/TL/TLOWERY/DBI-Shell-11.93.tar.gz Checking if your kit is complete... Looks good Writing Makefile for DBI::Shell cp lib/DBI/Shell.pm blib/lib/DBI/Shell.pm cp lib/DBI/Format.pm blib/lib/DBI/Format.pm cp lib/DBI/Shell/Timing.pm blib/lib/DBI/Shell/Timing.pm cp lib/DBI/Shell/SQLMinus.pm blib/lib/DBI/Shell/SQLMinus.pm cp lib/DBI/Format/SQLMinus.pm blib/lib/DBI/Format/SQLMinus.pm cp lib/DBI/Shell/FindSqlFile.pm blib/lib/DBI/Shell/FindSqlFile.pm cp lib/DBI/Shell/Completion.pm blib/lib/DBI/Shell/Completion.pm cp lib/DBI/Shell/Spool.pm blib/lib/DBI/Shell/Spool.pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" dbish.PL dbish Extracted dbish from dbish.PL with variable substitutions. cp dbish blib/script/dbish /usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)" blib/script/dbish Manifying blib/man1/dbish.1 Manifying blib/man3/DBI::Shell.3pm Manifying blib/man3/DBI::Format.3pm Manifying blib/man3/DBI::Format::SQLMinus.3pm /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/batch...ok t/coredubious Test returned status 0 (wstat 139, 0x8b) Executing /usr/bin/gdb "/usr/bin/perl" "core" (bt)... GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...(no debugging symbols found)... /root/.cpan/build/DBI-Shell-11.93/core: No such file or directory. (gdb) Hangup detected on fd 0 error detected on stdin after all the subtests completed successfully t/funcskipped all skipped: Function tests not completed t/shell...ok 32/51Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 361. t/shell...ok 35/51Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 361. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 364. t/shell...ok 38/51Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 361. t/shell...ok t/spool...ok t/sqlminusok 16/109Use of uninitialized value in array dereference at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/ExampleP.pm line 361. t/sqlminusok 20/109Use of uninitialized value in array dereference at /usr/lib/pe
Compile of DBD Solid
I am on a Solaris 2.8 system with a Solid 3.52 DB (embedded in Openview). I downloaded the SolidTechs library from their FTP site , uncompressed, untared and created a software link for libsolodbc.so referencing to soch1x30fe.sl in Solid lib directory. I already had Perl compiled and the DBI compiled because we are using the Oracle DBI/DBD already on this server. My perl Makefile.PL completes with no errors: # perl Makefile.PL Configuring DBD::Solid ... Remember to actually *READ* the README file! Especially if you have any problems. Using Solid in /usr/solid Found library files in /usr/solid/lib Found header files in /usr/solid/include Linking dynamically. Writing Makefile for DBD::Solid::Const Writing Makefile for DBD::Solid # Here is the error I am getting when I run the make: # make gcc -c -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris -I/usr/solid/include -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O-DVERSION=\"0.20a\" -DXS_VERSION=\"0.20a\" -fPIC -I/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE Const.c Running Mkbootstrap for DBD::Solid::Const () chmod 644 Const.bs rm -f ../blib/arch/auto/DBD/Solid/Const/Const.so LD_RUN_PATH="" gcc -G -L/usr/local/lib Const.o -o ../blib/arch/auto/DBD/Solid/Const/Const.so chmod 755 ../blib/arch/auto/DBD/Solid/Const/Const.so cp Const.bs ../blib/arch/auto/DBD/Solid/Const/Const.bs chmod 644 ../blib/arch/auto/DBD/Solid/Const/Const.bs Manifying ../blib/man3/DBD::Solid::Const.3 gcc -c -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris -I/usr/solid/include -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O-DVERSION=\"0.20a\" -DXS_VERSION=\"0.20a\" -fPIC -I/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE Solid.c In file included from Solid.h:57, from Solid.xs:7: /usr/solid/include/sqlext.h:398: warning: `SQL_INTERVAL_YEAR' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:58: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:399: warning: `SQL_INTERVAL_MONTH' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:59: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:400: warning: `SQL_INTERVAL_DAY' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:60: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:401: warning: `SQL_INTERVAL_HOUR' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:61: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:402: warning: `SQL_INTERVAL_MINUTE' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:62: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:403: warning: `SQL_INTERVAL_SECOND' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:63: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:404: warning: `SQL_INTERVAL_YEAR_TO_MONTH' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:64: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:405: warning: `SQL_INTERVAL_DAY_TO_HOUR' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:65: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:406: warning: `SQL_INTERVAL_DAY_TO_MINUTE' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:66: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:407: warning: `SQL_INTERVAL_DAY_TO_SECOND' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:67: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:408: warning: `SQL_INTERVAL_HOUR_TO_MINUTE' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:68: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:409: warning: `SQL_INTERVAL_HOUR_TO_SECOND' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:69: warning: this is the location of the previous definition /usr/solid/include/sqlext.h:410: warning: `SQL_INTERVAL_MINUTE_TO_SECOND' redefined /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/dbi_sql.h:70: warning: this is the location of the previous definition gcc -c -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris -I/usr/solid/include -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O-DVERSION=\"0.20a\" -DXS_VERSION=\"0.20a\" -fPIC -I/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE d
Re: Stored procedures and DBD::Sybase
On Mon, 2003-11-10 at 06:30, Steven Velez wrote: > Hello, > > I am using DBI v. 1.38, DBD::Sybase v. 1.01 (?), and FreeTDS 0.61.2 to > connect to an MSSQL 6.5 database from a Linux client and I am having > problems retrieving the values of out parameters to a stored procedure > call. MS-SQL doesn't handle OUTPUT parameters the same way as Sybase at the TDS protocol level, so you won't be receiving any CS_STATUS_RESULT return data. If you change your "print @c" to "select @c" you will get your data. As for multiple result sets - they will be returned to you in the order that they are generated, but here you are limited by FreeTDS's capabilities, as well as the fact that MS-SQL 6.x still talks TDS 4.2, rather than version 5 (Sybase) or 7/8 (MS_SQL 7.x and 2000). So in short you're going to have to find some other method of identifying result sets - possibly by using a dummy column: "select 'dummy'='status', 'data' = @c" Michael -- Michael Peppler Data Migrations, Inc. [EMAIL PROTECTED] http://www.mbay.net/~mpeppler Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or long term contract positions - http://www.mbay.net/~mpeppler/resume.html
Re: Oracle dbi ?
The problem is, these aren't actually SQL commands.
Rather, these are SQL*Plus commands. The DBD::Oracle
doesn't know what to do with these.
If you could figure out how to do this with OCI, then
you could probably patch DBD::Oracle to provide this
functionality.
Tim would appreciate that patch when you're done. :)
Jared
On Tue, 2003-11-04 at 07:03, Kevin Moore wrote:
> What user are you conneted as when you try to shut down the database?
> I've used shutdown, shutdown imediate, and in worst cases shutdown abort
> to stop an Oracle database. This has been the method (sql> ) from 8i
> forward.
>
> Kevin
>
> [EMAIL PROTECTED] wrote:
>
> >Since shutdown is not a sql command, has anyone figured out how to
> >shutdown a 8.1.7 or higher database
> >When you connect with:
> >$dbh=DBI->connect($tns,$connect,'',{ ora_session_mode => 2})
> >
> >Mike Bacovcin
> >Unix and Database administrator
> >Ch2mhill
> >[EMAIL PROTECTED]
> >720.286.2038
> >
> >
> >
> >
>
>
