Home > Archive > Tcl > October 2006 > What is a supported method for a Tcl application to access Sybase data?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
What is a supported method for a Tcl application to access Sybase data?
|
|
| Larry W. Virden 2006-10-30, 7:32 pm |
| There used to be a sybtcl extension, but from what I can see, there's
hasn't been, from what I can tell, a change in about five years to it.
So what alternatives are there? Of course, the first thing I had
suggested to me was "rewrite the app in Perl because Perl DBI is well
supported". Assuming that I'd rather leave that option open if nothing
else works.
| |
| Larry W. Virden 2006-10-30, 7:32 pm |
|
Gerald W. Lester wrote:
> Larry W. Virden wrote:
>
> Is sybtcl not working for you?
>
> Is there a problem with something being stable and bug free?
The issue is this - the developers are uncomfortable writing
applications that are dependant on an extension that they've been
unable to find any support for, they don't have
time/money/energy/interest in learning the 4000+ lines of C code well
enough to support it themselves, and they are facing migrating to a new
version of Sybase without confidence that the five plus year old code
will compile and work with the code.
I suggested they could just move forward and see if it would work.
They're considering rewriting all that Tcl code into Perl so they can
use DBI, which is actively supported .
| |
| Eckhard Lehmann 2006-10-30, 7:32 pm |
|
Gerald W. Lester wrote:
>
> So oratcl (which had a recent release because Oracle finally added something
> new to the API) and sytcl and etc should every year or so just bump there
> version number and do a new release with no changes since they have no new
> features (because the API under it has no changes) or no bug fixes (because
> no bugs have been erported)?
I suggest to write a short "hello" message (with some meaningful text,
of course) to the mailing list and see whether someone responds. If so,
it is probably supported ;-).
Eckhard
| |
| Pascal Scheffers 2006-10-30, 7:32 pm |
| Hi Larry,
Probably not the same problem, but my solution may work for you.
I'm running a Sybase SqlAnywhere Server on a Linux x86_64 box, aka
Adaptive Server Anywhere. ASA is NOT Adaptive Server Enterprise, the
main brand of sybase. Although it talks TDS 5.0 it doesn't like to
speak to FreeTDS (afaik, last checked a year ago), and sybtcl won't
compile, as ASA doesn't come with the client libs needed to compile.
I ended up directly linking the TclODBC extension to the Sybase
supplied ODBC driver, using either the UnixODBC or iODBC causes weird
results (on 64bit, 32 bit seems okay). I've been using it for about a
year now, no real problems.
However, if an ODBC driver is supplied with your database, just linking
it directly to tclodbc (not that hard, considering) could be a
solution. I think sybase also has a 'free' ODBC driver for ASE. I could
dig to supply more details on the compile process, but do be sure to
grab the latest tclodbc from CVS, don't use the sf.net downloadable
archives.
- Pascal.
(if you reply, be sure to CC pascal@scheffers.net, I might not see your
post otherwise)
Larry W. Virden wrote:
> There used to be a sybtcl extension, but from what I can see, there's
> hasn't been, from what I can tell, a change in about five years to it.
>
> So what alternatives are there? Of course, the first thing I had
> suggested to me was "rewrite the app in Perl because Perl DBI is well
> supported". Assuming that I'd rather leave that option open if nothing
> else works.
| |
| Pascal Scheffers 2006-10-30, 7:32 pm |
| Hi Larry,
Probably not the same problem, but my solution may work for you.
I'm running a Sybase SqlAnywhere Server on a Linux x86_64 box, aka
Adaptive Server Anywhere. ASA is NOT Adaptive Server Enterprise, the
main brand of sybase. Although it talks TDS 5.0 it doesn't like to
speak to FreeTDS (afaik, last checked a year ago), and sybtcl won't
compile, as ASA doesn't come with the client libs needed to compile.
I ended up directly linking the TclODBC extension to the Sybase
supplied ODBC driver, using either the UnixODBC or iODBC causes weird
results (on 64bit, 32 bit seems okay). I've been using it for about a
year now, no real problems.
However, if an ODBC driver is supplied with your database, just linking
it directly to tclodbc (not that hard, considering) could be a
solution. I think sybase also has a 'free' ODBC driver for ASE. I could
dig to supply more details on the compile process, but do be sure to
grab the latest tclodbc from CVS, don't use the sf.net downloadable
archives.
- Pascal.
(if you reply, be sure to CC pascal@scheffers.net, I might not see your
post otherwise)
Larry W. Virden wrote:
> There used to be a sybtcl extension, but from what I can see, there's
> hasn't been, from what I can tell, a change in about five years to it.
>
> So what alternatives are there? Of course, the first thing I had
> suggested to me was "rewrite the app in Perl because Perl DBI is well
> supported". Assuming that I'd rather leave that option open if nothing
> else works.
| |
| Pascal Scheffers 2006-10-30, 7:32 pm |
| Hi Larry,
Probably not the same problem, but my solution may work for you.
I'm running a Sybase SqlAnywhere Server on a Linux x86_64 box, aka
Adaptive Server Anywhere. ASA is NOT Adaptive Server Enterprise, the
main brand of sybase. Although it talks TDS 5.0 it doesn't like to
speak to FreeTDS (afaik, last checked a year ago), and sybtcl won't
compile, as ASA doesn't come with the client libs needed to compile.
I ended up directly linking the TclODBC extension to the Sybase
supplied ODBC driver, using either the UnixODBC or iODBC causes weird
results (on 64bit, 32 bit seems okay). I've been using it for about a
year now, no real problems.
However, if an ODBC driver is supplied with your database, just linking
it directly to tclodbc (not that hard, considering) could be a
solution. I think sybase also has a 'free' ODBC driver for ASE. I could
dig to supply more details on the compile process, but do be sure to
grab the latest tclodbc from CVS, don't use the sf.net downloadable
archives.
- Pascal.
(if you reply, be sure to CC pascal@scheffers.net, I might not see your
post otherwise)
Larry W. Virden wrote:
> There used to be a sybtcl extension, but from what I can see, there's
> hasn't been, from what I can tell, a change in about five years to it.
>
> So what alternatives are there? Of course, the first thing I had
> suggested to me was "rewrite the app in Perl because Perl DBI is well
> supported". Assuming that I'd rather leave that option open if nothing
> else works.
| |
| thelfter@gmail.com 2006-10-30, 7:32 pm |
| Haha, I have always been willing to issue support contracts for Oratcl.
I do not believe that Sybtcl is unsupported, but if someone wants to
assist me in setting up a sybtcl development environment. I could make
sure it stays updated with the changes to Tcl.
-Todd
On Oct 27, 8:14 pm, "Pascal Scheffers" <pascalscheff...@gmail.com>
wrote:[color=darkred]
> Hi Larry,
>
> Probably not the same problem, but my solution may work for you.
>
> I'm running a Sybase SqlAnywhere Server on a Linux x86_64 box, aka
> Adaptive Server Anywhere. ASA is NOT Adaptive Server Enterprise, the
> main brand of sybase. Although it talks TDS 5.0 it doesn't like to
> speak to FreeTDS (afaik, last checked a year ago), and sybtcl won't
> compile, as ASA doesn't come with the client libs needed to compile.
>
> I ended up directly linking the TclODBC extension to the Sybase
> supplied ODBC driver, using either the UnixODBC or iODBC causes weird
> results (on 64bit, 32 bit seems okay). I've been using it for about a
> year now, no real problems.
>
> However, if an ODBC driver is supplied with your database, just linking
> it directly to tclodbc (not that hard, considering) could be a
> solution. I think sybase also has a 'free' ODBC driver for ASE. I could
> dig to supply more details on the compile process, but do be sure to
> grab the latest tclodbc from CVS, don't use the sf.net downloadable
> archives.
>
> - Pascal.
>
> (if you reply, be sure to CC pas...@scheffers.net, I might not see your
> post otherwise)
>
> Larry W. Virden wrote:
>
| |
| Larry W. Virden 2006-10-30, 7:32 pm |
|
Gerald W. Lester wrote:
> sytcl and etc should every year or so just bump there
> version number and do a new release with no changes since they have no new
> features (because the API under it has no changes) or no bug fixes (because
> no bugs have been erported)?
Well, some kind of info, to the web site or mailing, letting people
know, when they mail questions, that answers are available, and that
problems will still be addressed (we reported problems last year
without ever getting anything other than an email saying that it wasn't
really supported any longer) would be nice. And, as new releases of
sybase were released, perhaps a note to the mailing list or something
indicating that things were working just fine, would also be a pleasant
difference.
Anyways, with no code changes, no mailing list message discussion, etc.
the appearance of death is enough to scare the developers away from the
extension. If it doesn't scare you, wonderful! I'm just hoping to find
a tcl solution that will lessen the amount of rewriting necessary.
Thanks for all your emails.
|
|
|
|
|