| Thread | Last Post | Replies |
|
| Sybase::DBlib manual page synopsis has no error checking | 31 Mar 2004 12:20 GMT | 3 |
The synopsis at the top of Sybase::DBlib's pod documentation is a poor example to follow because it does no error checking. IMHO, it would be better to show code that checks the status returned from each call.
|
| last_insert_id() | 30 Mar 2004 12:12 GMT | 4 |
Tim, I ran into some problems with last_insert_id() while trying to implement it for DBD::mysql 3.0. I have subjoined a patch against DBI 1.42 with the changes that I made so that I could get last_insert_id() working from the
|
| fetchrow_hashref issue | 29 Mar 2004 21:56 GMT | 5 |
I'm using DBD::Sybase 1.01 with FreeTDS 0.62.dev.20031109 to connect to an MSSQL 7.0 server using TDS protocol 4.2. I am experiencing issues with hashref 'key' names which appear to be corrupted and/or holding stale characters from previous data sets. The issue
|
| Very Odd Problem | 29 Mar 2004 21:44 GMT | 7 |
The following code appears to work as expected: 1 #!/usr/local/bin/perl 2 3 # Subroutines
|
| Version compatibility | 29 Mar 2004 18:27 GMT | 1 |
I'm looking into upgrading from ASE 12.0 to ASE 12.5.1, and am trying to figure out a few things regarding our installation of Sybperl. I understand that it was built with an "old" version of Sybase Open Client. I have tried doing: ct_config(CS_GET, CS_VERSION,...)
|
| Problems compiling Sybperl 2.16 on Solaris 9 | 29 Mar 2004 14:56 GMT | 6 |
Got the following errors in make test: t/2_ct_xblk............ Open Client Message: Message number: LAYER = (0) ORIGIN = (0) SEVERITY = (0) NUMBER = (0)
|
| Driver capabilities metadata ? | 29 Mar 2004 12:30 GMT | 1 |
I don't see anything in the PODs, so... Is there any std. mechanism for querying a driver regarding its capabilities ? E.g., similar to get_info(), but related to driver behavior, rather than supported DBMS behavior.
|
| New Oracle "Instant Client" | 25 Mar 2004 22:50 GMT | 7 |
http://otn.oracle.com/tech/oci/instantclient/instantclient.html "Download and be ready in seconds. Deploy your applications right out of the box. Deliver the promise. Free. Instant Client allows you to run your applications without installing
|
| Multiple result sets and the $sth->more_results method | 25 Mar 2004 16:59 GMT | 7 |
Here's what I'm thinking of with respect to $sth->more_results: Principles: 1: At any point in time the state of a statement handle corresponds with having executed one 'sub-statement' within the 'compound-statement'.
|
| DBI and character sets (yet again) | 22 Mar 2004 09:49 GMT | 1 |
(Note: I'm sending this to both -users and -dev, I'm not certain which it belongs to at this point) I'm building a heterogenous multidatabase tool, and am curious as to how various DBD's are handling
|
| Driver Inquiry for HSQLDB | 20 Mar 2004 21:25 GMT | 2 |
I'm doing preliminary work on writing a driver for the pure java SQL Database "HSQLDB" (based upon the old Hypersonic SQL database), available at http://hsqldb.sourceforge.net. HSQLDB is a 100% java, full featured SQL Database that I've found to be extremely powerful for
|
| ct_param problem | 19 Mar 2004 19:35 GMT | 6 |
I recently upgraded from DBD-Sybase-0.91 and DBI-1.14 to DBD-Sybase-1.02 and DBI-1.40 I tried to use 12.5.1 open client to connect to a 12.0 ASE server (we are in transition from 12.0 to 12.5.1) but that was giving me the error
|
| DBI package that supports Oracle encryption | 17 Mar 2004 14:47 GMT | 1 |
Is it possible for anyone to confirm which version of DBI would work with oracle SQLNET encryption? We are using DBI verison 1.06 and not able to connect when encryption is enabled.
|
| [dbi-dev] Proposed fetchall_hashref and selectall_hashref extensions | 16 Mar 2004 00:00 GMT | 6 |
DBI Developers,
> Speak before you patch I would like to extend DBI's fetchall_hashref and selectall_hashref methods to handle multiple keys. Being new to DBI, I miss Michael Peppler's
|
| Retrieving current statement with $dbh->errstr | 12 Mar 2004 15:50 GMT | 1 |
I'm migrating all of our ksh scripts to perl. I'm new to DBI. I'm testing it to see if it'll work for all of the existing db access currently found in our ksh scripts. If there's a better place to post this question, thanks in advance for the direction. I'd like the current sql ...
|