i saw that the sybperl - peppler
> list is not active..
>
> thanks in advance
> Uwe
>
>
--
Michael Peppler
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
"A successful [software] tool is one that was used to do something undreamed of
by its author." -- S. C. Johnson
gt; a date column is chopping off the time when it is midnight. Also, if the
>> date is 1/1/1900, its only outputting the time, without the date at all.
>> We've tried multiple versions of DBD, still no luck. Any suggestions?
>> I’m using DBD version 1.622 btw…
>>
il is strictly
> prohibited
> and may be unlawful. If you have received this E-mail in error, please
> notify the
> sender immediately and permanently delete the original and any copy of this
> E-mail
> and any printout. Thank You.**
>
> References
>
> V
There was a change in 1.11 (I think) to handle utf8/unicode data. THis
included forcing the charset to utf8 in the client.
You can go back to the old behavior if you edit dbdimp.c and change or
comment out the following:
if (retcode == CS_SUCCEED) {
if ((retcode = cs_local
penClient. If you are using DBD::Sybase with FreeTDS then you may need to use
another private attribute, maybe something like
defined($dbh->{syb_dyn_supported}).
Michael
--
Michael Peppler
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
"A successful [software] tool is one that was used to do something undreamed of
by its author." -- S. C. Johnson
On Jun 3, 2010, at 8:14 PM, Dave Rolsky wrote:
> On Thu, 3 Jun 2010, Michael Peppler wrote:
>
>> Which version of Sybase, which version of Sybase OpenClient, and which
>> version of DBD::Sybase?
>
> Ah, I was using the old libs (11.0), which may have been the problem.
On Jun 3, 2010, at 7:29 PM, Michael Peppler wrote:
> Hi,
>
> Which version of Sybase, which version of Sybase OpenClient, and which
> version of DBD::Sybase?
>
> Are you setting the connection charset to utf8 (in the connect() call?)
>
I just gave this a try - I&#x
ecode( 'utf8', $chars );
>
> So the data is there, but not in a very usable form.
>
> Has anyone researched or solved this problem?
>
> Michael Peppler, if you're reading this, is there any work on supporting
> Perl's unicode format transparently in DBD::S
ssary serialization may occur due to hash collisions, but I'm not too
> worried about it and can always increase the # buckets if needed.
>
> This seems to work in testing. Just wanted to find out if it makes sense, if
> there's a CPAN module that already does this (couldn&#
It's hard to tell for sure what could be wrong.
First, I would try to check that the Sybase related env. variable are
correctly seen when you are in the dbi-link script.
Second - you may run into an insurmountable problem: Sybase open
client installs its own signal handler to do a number of thing
st this to the freetds mailing list to get a better answer.
Michael
--
Michael Peppler -Peppler Consulting
SaRL
mpepp...@peppler.org - http://www.peppler.org
Sybase DBA/Developer - TeamSybase: http://www.team
RGE_FILES USE_PERLIO USE_REENTRANT_API
Built under solaris
Compiled at Dec 28 2008 00:07:21
%ENV:
PERL5LIB="/sa/common/lib/5.10.0"
@INC:
/sa/common/lib/5.10.0/sun4-solaris-thread-multi
/sa/common/lib/5.10.0
/home/persicom/perl.v5.10.0/lib/5.10.0/sun4-solaris-thread-multi
/
"
at ./
web_issues.cgi line 102.
Rats - there's a typo in the man page. Try $sth->syb_ct_finish_send()
instead.
Michael
--
Michael Peppler -Peppler Consulting
SaRL
[EMAIL PROTECTED] - http://www.peppler.org
Sybase DB
*
*** 545,550
--- 545,551
else
retcode = CS_SUCCEED;
+ sv_catpv(DBIc_ERRSTR(imp_dbh), " ");
return retcode;
} else {
if(srvmsg->msgnumber) {
Thanks - I'll get that into the next release.
Michael
--
Michael Pepp
and somewhere near the top add:
#define BLK_VERSION_150 BLK_VERSION_100
#define BLK_VERSION_125 BLK_VERSION_100
#define BLK_VERSION_120 BLK_VERSION_100
Michael
--
Michael Peppler - Peppler Consulting SaRL
[EMAIL PROTECTED] - http://www.pe
ated as a
really serious issue.
Michael, any chance you could review this and get it (or a better fix)
released soonish?
The fix looks reasonable, but I think what you are seeing might be an
indication of a deeper problem when the connection is abruptly lost.
Normally the connection s
$total ) = $dbh->selectrow_array( $sth, undef, $id );
I was able to reproduce it. I don't know yet if this is a DBD::Sybase
problem or something else. Unfortunately I don't have much time to debug
this.
Michael
--
Michael Peppler - Peppler Consul
lvalue in
assignmentSybase.xsi: In function
'XS_DBD__Sybase__db_DESTROY':Sybase.xsi:336: error: invalid lvalue in
assignmentmake: *** [Sybase.o] Error 1
I haven't tried the recent DBI versions yet, so I need to look into
this, but it will take me a week or more (AFK next week).
Michael
--
Michael
D::Sybase::db::_login called at
/usr/lib/perl5/site_perl/5.8.3/x86_64-linux-thread-multi/DBD/Sybase.pm
line 90.
At first look it appears that DBD::Sybase isn't installed correctly.
Did you get any errors during the install process?
Did "make test" work correctly?
.cpan.org/~mewp/DBD-Sybase-1.08/> (5
Reviews <http://cpanratings.perl.org/d/DBD-Sybase>) - 21 Apr 2007 -
Michael Peppler <http://search.cpan.org/~mewp/>
One of the files named: Makefile_PL has an include statement, which
includes a file that does not exist
Ie: requir
uates to 0 in a numerical context ($sth - 0), which returns a
number.
Michael
--
Michael Peppler - Peppler Consulting SaRL
[EMAIL PROTECTED] - http://www.peppler.org
Sybase DBA/Developer - TeamSybase: http://www.teamsybase.com
Sybase on Linux FAQ - http://www.peppler.org/FAQ/linux.html
ase, so that it finds
/home/sybase/config/objectid.dat.
Michael
--
Michael Peppler - Peppler Consulting SaRL
[EMAIL PROTECTED] - http://www.peppler.org
Sybase DBA/Developer - TeamSybase: http://www.teamsybase.com
Sybase on Linux FAQ
y do you want to 'use DBD::Sybase' given that the working example shows that
it is not necessary to do so?
If you were importing some specific symbols from DBD::Sybase, it would make
sense - but you aren't self-evidently doing that, so it doesn't
AGE columns can't be used with
placeholders, just as they can't be used as parameters to stored procedures.
The DBD::Sybase docs discuss this, and the proprietary way of
updating/inserting TEXT/MAGE data without embedding it in the SQL
statements.
Michael
--
Michael Peppler
In 1.08 the only check is for ASE - so if you pass in anything else then
fetching @@version and a few other things will not be done.
In the next release you can also pass in RA - for ReplicationAgent. This
will also turn off all ct_options() calls. I needed this to be able to
talk to the Sybase
I believe that there is a bat file that will either rename or add new
copies of the libraries with the old names.
However, as OpenClient has changed a bit I would not be 100% confident
that the binary built for 12.5.x will work with OCS 15.
Michael
Extranet
[EMAIL PROTECTED] - 11.09.2007 23
YOu need to upgrade your DBD::Sybase package - version 1.08 handles this
correctly.
Michael
Extranet
[EMAIL PROTECTED] - 29.08.2007 10:15
To: dbi-users
cc:
Subject:Number of row fields inconsistent with NUM_OF_FIELDS,
NUM_OF_FIELDS updated
I'm currently moving a perl script
You should always specify if you are using Sybase or FreeTDS client
software - I'm guessing the latter.
You can work around the issue by adding a #define for CS_LOGIN_STATUS in
dbdimp.c. Alternatively this may already have been solved in a more recent
version of FreeTDS - you should probably ch
Unfortunately in DBD::Sybase 1.08 I removed some code that allowed it to
work with older DBI versions.
DBD::Sybase 1.08 requires a fairly recent version of DBI (I haven't check
the exact version). If you upgrade your DBI to the current version you
should have no problems.
Michael
Extranet
You should run this with DBI->trace() turned on to see what DBD::ODBC
actually does. The temp tables should only be dropped when the connection
is closed.
Michael
Extranet
[EMAIL PROTECTED] - 11.05.2007 00:19
To: martin.evans, dbi-users
cc:
Subject:RE: temporary table "disape
First questions first...
Do you have a Sybase client installed ?
If so, make sure that your SYBASE env. variable points at the Sybase root
directory, and make sure that you have sourced the SYBASE.sh file that is
found in that directory.
Once that is done you should have it a lot easier.
Mich
I'm pretty sure that #tmp is a local temporary table, and ##tmp is a
global temporary table...
So the original problem is most likely that the create table #tmp and the
insert into #tmp statements aren't being run on the same physical
connection. I don't know DBD::ODBC, but I can tell you that
You can probably build freetds for this, but this will limit the
functionality of DBD::Sybase as FreeTDS doesn't offer all the features of
OpenClient (and is mostly tested against MS-SQL rather than Sybase ASE).
Michael
Internet
[EMAIL PROTECTED] - 30.04.2007 23:06
To: Mi
I presume that you are on a 64bit version of Linux.
If that's the case, then you have two choices:
1. Rebuild perl (and all the other XS extensions that you use) in 32bit
mode
or
2. Find 64 bit libraries for Sybase. These exist, but are not free. You
should be able to buy a "developer" editio
or syb_xxx methods.
610 - Segfault when using signals with the threaded libraries and
perl >= 5.8.
As always, bug fixes, comments, etc. are welcome!
Michael
--
Michael Peppler - Peppler Consulting SaRL
[EMAIL PROTECTED] - h
Matthew Persico wrote:
On 4/10/07, Michael Peppler <[EMAIL PROTECTED]> wrote:
All,
I'm finally getting closer to releasing the DBD::Sybase 1.08, which will
have a number of fixes.
I would like to encourage those of you who have the time and the
resources to please download and inst
.8.
Thanks,
Michael
--
Michael Peppler - Peppler Consulting SaRL
[EMAIL PROTECTED] - http://www.peppler.org
Sybase DBA/Developer - TeamSybase: http://www.teamsybase.com
Sybase on Linux FAQ - http://www.peppler.org/FAQ/linux.html
You used the 32bit libraries with a 64bit version of perl - this will NOT
work.
You either need to install a 64bit version of the Sybase client (SDK), or
install a 32bit version of perl.
Michael
Extranet
[EMAIL PROTECTED]@sea.gmane.org - 20.03.2007 17:42
Sent by:[EMAIL PROTECTED]
That's the most recent - AFAIK.
I don't know of any other source (and note that I don't build these myself
- they have been contributed to me)
Michael
Extranet
[EMAIL PROTECTED] - 08.03.2007 03:36
To: dbi-users
cc:
Subject:Re: ppms
On 3/7/07, Matthew Persico <[EMAIL PROTECTE
First of all you are using really old Sybase code - you can download
current Sybase code from http://www.sybase.com/linux_promo.
Second, you didn't specify a database server to connect to, nor a user
and/or password to use when connecting to that server, so DBD::Sybase will
attempt to connect t
I'm not sure about the first error (x86_64-pld-...), though I suspect that
this is a particular build of perl.
The second is simpler - you don't have libct.so installed (the Sybase
Client Library lib).
In this case I suspect that the RPM expects to have the FreeTDS version of
Client Library in
Forwarded message --
From: Matthew Persico <[EMAIL PROTECTED]>
Date: Nov 20, 2006 12:45 PM
Subject: Re: Can't connect to Sybase Rep server
To: Michael Peppler <[EMAIL PROTECTED]>
Well, it's been more than a week. :-) No, I have not been on jury duty
THAT long, bu
And some drivers have a "timeout" parameter that handles this issue at the
vendor API level (e.g. DBD::Sybase's "timeout" parameter that is handled
internally by OpenClient).
Michael
Extranet
[EMAIL PROTECTED] - 19.09.2006 15:37
To: henri
cc: tyler, darnold, Tim.Bunce, dbi-users,
You are trying to link 32bit code with 64bit code. You either need to get
the 64bit version of the Sybase client libraries, or rebuild perl in 32bit
mode.
Michael
Extranet
[EMAIL PROTECTED] - 09/09/2006 00:48
To:dbi-users
cc:
Subject:trouble loading DBD sybase, 1_07_01
Hi,
I am
Ah! I think I know what happens...
You probably have the syb_flush_finish attribute turned on - which means
that DBD::Sybase will try to fetch all the results that are pending for the
active sth.
I'm going to have to look at the code to see how that could be invalidated
(or fixed!)
Michael
E
Here's a little test:
#!/usr/bin/perl
use DBI;
my $dbh = DBI->connect('dbi:Sybase:server=DBA_SQL', '...', '...');
my $sth = $dbh->prepare("select * from histo..table_size where serverName =
'BPSREC5_SQL'");
$sth->execute;
DBI->trace(5);
undef $dbh;
This produces the following:
DBI 1.51-ithr
There is no configuration that can be done at the DBD::Sybase level for the
BLK handling - if you are limited to 255 chars then it is most likely a
limitation of the BLK api implementation of FreeTDS.
Michael
Extranet
[EMAIL PROTECTED] - 21/08/2006 15:39
To:Michael PEPPLER
cc
DBD::Sybase will support whatever the underlying client libs are capable of
handling.
Michael
Extranet
[EMAIL PROTECTED] - 21/08/2006 15:27
To:fumiakiy
cc:dbi-users
Subject:Re: "max" datatypes support of SQL Server 2005 for DBD-ODBC
Fumiaki Yoshimatsu wrote:
> I had a need t
DBD::Sybase does not handle character conversions - this is done at the
OpenClient level (i.e. FreeTDS in your case).
Make sure that the locale that is set for your two servers are the same,
and that the charset that is defined on the database server (run
sp_helpsort in a SQL command window).
Mic
ow what it refers to there isn't all that much that I can
do at this point.
If the OP can provide me with a trace that illustrates the problem then
it may be possible to identify the issue.
Michael
--
Michael Peppler - Peppler Consulting SaRL
[EMAIL PROTECTED] - http://www.peppler.o
Hi,
I have no knowledge of the DBIx::ContextualFetch module, and so have no
idea whether upgrading DBD::Sybase could fix the problem.
The issue could be related to multiple-result sets, or to some other
Sybase-specific issue that isn't handled properly by DBIx::ContextualFetch,
or maybe something
The sp_configure option is dynamic, but only affects future connections. It
is an upper limit, and the client has to specifically request the larger
packet size to get it. Otherwise the default 512 byte packet size is used.
Michael
Extranet
[EMAIL PROTECTED] - 23/06/2006 14:48
To:matthew.
I suspect that this should really be addressed to a Sybase list.
However, what may happen is that the server doesn't have enough network
memory available and therefore is not able to allow the client to connect
with the 16k packet size.
You should probably take a look at the "additional network m
Hi,
Yes, I know about that script - but you should still be careful when you
use a binary built with a 12.5.1 client installation against a 15.0
run-time. It would probably be better to rebuild.
Michael
Extranet
[EMAIL PROTECTED] - 25/04/2006 17:13
To: Michael PEPPLER
cc: dbi
You can interact with an ASE 15 server with a 12.5.1 client with no
particular problems. There may be some issues with the more esoteric
OpenClient functionality, but as DBD::Sybase doesn't use this it shouldn't
be a problem.
So the short answer is that you can keep your current environment and ad
Here's the code that checks to see if the remote server understands the
ct_option call.
/* Check to see if the server supports the ct_option() call */
if(!imp_dbh->optSupported) {
CS_BOOL val;
CS_RETCODE ret = ct_capability(connection, CS_GET,
On 2/23/06, Chuck Fox <[EMAIL PROTECTED]> wrote:
>
> Hello fellow dbi-users.
>
> I am attempting to connect to a 12.5 Sybase server using kerberos
> enabled connections. My isql and sqsh both correctly connect (sqsh
> needed a small fix to load the security ). However, I am unable to get
> DBD::S
be hidden from the user...
Michael
Extranet
[EMAIL PROTECTED] - 27/02/2006 20:39
To:dbi-users, Michael PEPPLER
cc:
Subject:Can't connect to Sybase Rep server
This simple test program:
use strict;
use warnings;
use DBI;
my $dbh = DBI->connect('dbi:Sybase:server=REPP&
SERVER', );
Of course you should already have seen this and added the entry to
freetds.conf when you were building DBD::Sybase as it is required for
the "make test" phase.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer - TeamSybase: http://www.teamsybase.com/
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
Please post the build log (perl Makefile.PL and make)
Thanks,
Michael
Extranet
[EMAIL PROTECTED] - 01/02/2006 19:34
To:dbi-users
cc:
Subject:Re: trouble loading DBD::Sybase 1.05 on tiger, MacOSX 10.4.4
Hi,
I tried your solution on a newer version (1.07) of the install..it did
> > > For this purpose, "connected" and "pingable" are the same thing.
> >
> > Yes and no. If you can't ping the server, but the TCP socket is
> > still open, that means you essentially have this TCP connection to the
> > server that's not being used, in an open state, for the rest of the
lifet
Take a look at this link and let me know if that fixes things:
http://groups.google.ch/group/sybase.public.macosx/browse_thread/thread/58a37c62080397dd/d22a38db2705d421?lnk=st&q=dbd%3A%3Asybase+macosx&rnum=1&hl=fr#d22a38db2705d421
Michael
Extranet
[EMAIL PROTECTED] - 31/01/2006 21:25
To:
Yes.
Michael
Extranet
[EMAIL PROTECTED] - 03/01/2006 02:14
To:dbi-users
cc:
Subject:DBD::Sybase Stored Proc argument placeholders
In 1.00 (which I have in production) Stored Proc argument placeholders
are marked as experimental. By 1.07, the designation has been removed.
Can I s
anks again for your assistance.
Rick
-----Original Message-
From: Michael Peppler [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 22, 2005 11:51 AM
To: [EMAIL PROTECTED]
Cc: dbi-users@perl.org
Subject: Re: DBD-Sybase 1.07, FreeTDS 0.63, HPUX 11.11: Build problem
(maketest)
On Wed, 2005-12
DBI-1.48. The "make test" appears to
> fail because it tries to use a non-existent (standard) Sybase server and
> connect params.
Did you give it a valid server name during the configuration phase of
the build?
Is that server correctly defined in the freetds.conf file?
Is the SYB
One way to solve it is to do:
use DBI qw(:sql_types);
Michael
Extranet
[EMAIL PROTECTED] - 12/12/2005 00:45
To:dbi-users
cc:
Subject:Bareword "DBI::SQL_INTEGER" not allowed while "strict subs"
I am new to DBI, Perl, and SQL and I am currently trying to piece
together a group of
On Thu, 2005-11-03 at 21:10 +0100, Michael Peppler wrote:
> On Thu, 2005-11-03 at 11:53 -0500, [EMAIL PROTECTED] wrote:
> > I have problem loading the DBD-Sybase-1.07 on Unix/Solaris 8 OS, SUN
> > Fire V880 hardware.
> >
> > The perl Makefile.PL and the make comm
, or use DBD::Sybase
1.04.
I will add a configuration option to skip the BLK calls if the library
is unavailable in a future version.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer - TeamSybase: http://www.teamsybase.com/
Sybase on Linux FAQ: ht
I build DBD::Oracle with instantclient on linux with no particular problems
after following one of the recipies that I found googling for it.
On the other hand I couldn't get this to work on HP-UX, always getting the
OCIClientInitialize error, no matter which combinations of env. variables
and per
t see why that would happen.
If you can connect with isql you should be able to connect with
DBD::Sybase, as long as your environment is the same.
Try running this with DBI->trace(5) and send me (not the list) the
output.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.pepple
TECTED] - 19/08/2005 13:57
Please respond to [EMAIL PROTECTED]
To:Michael PEPPLER
cc:martin.evans, dbi-users
Subject:RE: [dbi] DBD::Oracle, Instantclient and HP-UX...
Tree setting SHLIB_PATH to the same value as LD_LIBRARY_PATH. Try doing
this before you build DBD::Oracle. (You
Thanks Martin,
Unfortunately unsetting ORACLE_HOME didn't fix that problem (i.e.
OCIEnvCreate still fails).
Michael
Extranet
[EMAIL PROTECTED] - 19/08/2005 10:43
To: dbi-users
cc:
Subject:RE: [dbi] DBD::Oracle, Instantclient and HP-UX...
Michael,
I think with InstantClien
Hi,
I'm not exactly new to DBI, but I am *very* new to Oracle, so please bear
with me...
I'm trying to build DBD::Oracle on an HP-UX (11.11) box with the 32bit
instantclient package, and while the build works the make test fails, and
my googling has failed to turn up any solutions.
I've patch
-- NOT OK
>
> What am I missisng?
It looks like your perl installation is broken... Can you build other
extensions that require compilation?
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
ytes
md5: 8648a37840b362eb860146627e8aac45
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
needs to change that much.
Certainly the Sybase driver won't be able to support many of the
proposed functionality, or won't benefit from the changes (i.e. no speed
gain, no improved flexibility, etc).
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
DBD::Sybase 1.04.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
err=-1
> ) at ...
>
> is there some workaround for this, or I have to read all into memory ?
The work-around is to open a second connection to the server and use
that in the inner function. Be careful not to create a sequence of SQL
calls that causes a deadlock.
Michael
--
Michael Pep
[ODBC SQL Server Driver]Invalid
> charact
> er value for cast specification (SQL-22018)(DBD: st_execute/SQLExecute
> err=-1) a
> t ... line 291.
That's a database server error - you need to look this up in the MS-SQL
documentation and from there figure out what is wrong with your SQL.
is benign.
The other errors are also expected, because FreeTDS doesn't yet support
all the features of Sybase's OpenClient libraries.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
he same
information that an ODBC or JDBC driver would get.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
hat moves the conversion from the client to the server.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
MS SQL). In this case the value returned
> would be from the last non-placeholder insert statement.
>
> So I will to have using "select max($field) from $table" 'method' ?
No - just do a "select @@identity" to get the latest value.
Michael
--
Michael Peppler
In your case you should get 11.1.1 instead of the 15.0, and probably
some EBF string.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
d reference to
> _CFBundleGetBundleWithIdentifier expected to be defined in a dynamic
> image
A little googling goes a long way...
http://groups-beta.google.com/group/sybase.public.macosx/browse_thread/thread/58a37c62080397dd/d22a38db2705d421?q=_CFBundleCopyBundleURL&rnum=2#d22a3
I've just uploaded DBD::Sybase 1.05_01 (a test/development version) to
CPAN and to http://www.peppler.org/downloads/
This version fixes a number of problems with AutoCommit, and some
additional small-ish issues. If you have the time please give this
version a try.
Thanks,
Michael
--
Mi
; Consequently, AFAIK, almost no one in the sybase world use them.
That's not quite true.
Placeholders in Sybase are well supported, with the notable exceptions
that you can't use them for TEXT or IMAGE (i.e. BLOB)
columns/parameters.
Michael
--
Michael Peppler - [EMAIL PROTECT
b=HASH(0x8fd1834)->{User}: unrecognised attribute or
> > invalid value at //ms/dist/perl5/PROJ/DBI/1.42-5.8/lib/perl5/DBI.pm line
> > 634, chunk 1.
> >
> >
> > NOTICE: If received in error, please destroy and
'll take a look at it - but as I don't really do anything fancy with
error handlers in the code I would expect this to work the same way as
isql.
Ping me again in a few days if you haven't heard from me on this.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.pep
s the result status of a stored
> procedure from coming back as a row when using
> fetchall_arrayref?
Yes, see the syb_doProcStatus attribute.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
On Tue, 2005-01-11 at 08:05, Daniel Kasak wrote:
> Michael Peppler wrote:
>
> >The FreeTDS ODBC drivers support placeholders, IIRC.
> >
> >
> Are you *sure*?
>
> That's what I'm using at the moment ... DBD::Sybase with FreeTDS.
DBD::Sybase with
researched a bit:
>
> I'm currently using DBD::Sybase with freetds, but this doesn't support
> placeholders.
> I had a quick look at DBD::ADO but it only runs on Win32.
> DBD::ODBC requires an ODBC manager, and I'm doing this on the cheap ( ie
> opensource on
nfortunately as I've started
to set the locale in the context, rather than the connection. As this
functionality doesn't work with FreeTDS anyway you can simply comment
out the warning in the syb_init() call in dbdimp.c and rebuild.
Michael
--
Michael Peppler - [EMAIL PROTECTED] -
et AutoCommit=>1 to solve this problem.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html
PL fails if umask is 0.
578 - Better warning for calling $dbh->{LongReadLen} if $dbh is busy.
572 - Minor documentation update for bind_param().
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
Available for contract work - http://www.peppler.org/resume.html
ils three tests under Tru-64.
577 - perl Makefile.PL fails if umask is 0.
578 - Better warning for calling $dbh->{LongReadLen} if $dbh is
busy.
572 - Minor documentation update for bind_param().
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://
tter case
select ...
from foo, bar
where foo.id = bar.id
.
will fetch rows from "foo" first, and then do a nested iteration to
fetch matching rows from "bar". This is useful if we know that fetching
rows from "foo" is expensive *and* we know that only a
;, "beta", "zeta"
> "omega" in that column, $dbh->{LongReadLen} will be set to "zeta". I
> don't think that will buy us anything good. You want the *length* of the
> *longest* string, not the string that sorts last in the word list. So,
ll return valid data for
SELECT statements right after the last row has been fetched.
$sth->rows will return correct data immediately after execute() for
INSERT/UPDATE/DELETE statements.
Michael
--
Michael Peppler - [EMAIL PROTECTED] - http://www.peppler.org/
Sybase DBA/Developer
ng the
charset, etc. that happen prior to the actual connection being open.
So even if you create a generic mechanism for building DSNs there will
be a lot of stuff that won't work, or will need a whole host of
exceptions and special handling.
Michael
--
Michael Peppler - [EMAIL PROTECTED
1 - 100 of 467 matches
Mail list logo
