Free sybase software for linux

Sybase::Xfer contains Bcp data into a Sybae table from multiple sources.

SYNOPSIS

#!/usr/bin/perl
use Sybase::Xfer;
my %switches = (-from_server=>CIA, -to_server=>NSA, -table => x-files);
my $h = Sybase::Xfer->new( %switches );
my %status = $h->xfer(-return=>"HASH");
print "xref failed. $status{last_error_msg}n" unless $status{ok};

#!/bin/ksh
sybxfer -from_server CIA -to_server NSA -table x-files
if [[ $? != 0 ]]; then print "transfer problems"; fi

Persistent::Sybase is a persistent class implemented using a Sybase database.

SYNOPSIS

use Persistent::Sybase;
use English; # import readable variable names like $EVAL_ERROR

eval { ### in case an exception is thrown ###

### allocate a persistent object ###
my $emp = new Persistent::Sybase($data_source, $username, $password, $table);

### define attributes of the object ###
$emp->add_attribute(empno, ID, Number, undef, 4);
$emp->add_attribute(ename, Persistent, VarChar, undef, 10);
$emp->add_attribute(job, Persistent, VarChar, undef, 9);
$emp->add_attribute(mgr, Persistent, Number, undef, 4);
$emp->add_attribute(hiredate, Persistent, DateTime, undef);
$emp->add_attribute(sal, Persistent, Number, undef, 7, 2);
$emp->add_attribute(comm, Persistent, Number, undef, 7, 2);
$emp->add_attribute(deptno, Persistent, Number, undef, 2);

### query the datastore for some objects ###
$emp->restore_where(qq{
sal > 1000 and
job = CLERK and
ename LIKE M%
}, "sal, ename");
while ($emp->restore_next()) {
printf "ename = %s, emp# = %s, sal = %s, hiredate = %sn",
$emp->ename, $emp->empno, $emp->sal, $emp->hiredate;
}
};

if ($EVAL_ERROR) { ### catch those exceptions! ###
print "An error occurred: $EVAL_ERRORn";
}

ABSTRACT

This is a Persistent class that uses a Sybase database table to store and retrieve objects. This class can be instantiated directly or subclassed. The methods described below are unique to this class, and all other methods that are provided by this class are documented in the Persistent documentation. The Persistent documentation has a very thorough introduction to using the Persistent framework of classes.

DBIWrapper is a Perl Module that provides for easier access to databases using DBI. It supports MySQL, PostgreSQL and ODBC DBD modules. High level methods for reading and writing to the database are provided. DBI data structures or XML are returned
Main features:
- The DBIWrapper is a Perl Module which provides easier access to databases using DBI. It currently supports MySQL, PostgreSQL, Sybase and ODBC DBD drivers. High level methods for reading, writing, commiting and rolling back transactions are provided. The DBI data structures can still be used to return the data in.
- XML Support is now available as of DBIWrapper 0.16. Using readXML() you can have the result of your SELECT statement be returned as an XML document (format defined here) which will describe the SELECT statement issued and the rows of data returned from the backend.
- DBIWrapper::XMLParser included in DBIWrapper 0.17! This module parses the XML generated by readXML() and returns a perl data structure in the DBIWrapper::ResultSet module. This makes for extremely easy manipulation of your database data. DBIWrapper::XMLParser relies on XML::LibXML. See README for details.
- HTML Support is now available as of DBIWrapper 0.20. Using readHTML() you can have the result of your SELECT statement returned as an HTML snippet which is fully customizable via CSS. See the man page for more details.
- Sybase Support is now available as of DBIWrapper 0.22!
- Helper methods getDataArray(), getDataHash(), getDataArrayHeader(), getDataHashHeader() do the work of read() and then build up an array with the returned result set. See the man page for more info.
Enhancements:
- DBD::Sybase is now officially supported and the getData... methods (getDataArray, getDataArrayHeader, getDataHash, getDataHashHeader) all know how to properly handle the possible multiple result sets that Sybase can return. getID() was added for returning the ID of the last inserted row.

CA::AutoSys is a Perl interface to CAs AutoSys job control.

SYNOPSIS

use CA::AutoSys;

my $hdl = CA::AutoSys->new( [OPT] ) ;
my $jobs = $hdl->find_jobs($jobname) ;
while (my $job = $jobs->next_job()) {
:
}
my $status = $job->get_status() ;
my $children = $job->find_children() ;
while (my $child = $children->next_child()) {
:
}

CLASS METHODS

new()
my $hdl = CA::AutoSys->new( [OPT] ) ;

Creates a new CA::AutoSys object.

Below is a list of valid options:

dsn

Specify the DSN of the AutoSys database server to connect to. If nothing is specified, Sybase will be assumed: dbi:Sybase:server= With this option you should be able to connect to databases other than Sybase.

server

Specify the AutoSys database server to connect to. Either this option or the dsn option above must be given. Please note, that when specifying this server option, a Sybase database backend is assumed.

user

Specify the database user. With an out-of-the-box AutoSys installation, the default user should work.

password

Specify the database password. With an out-of-the-box AutoSys installation, the default password should work.

Example:

my $hdl = CA::AutoSys->new(server => "AUTOSYS_DEV");

AxKit::XSP::ESQL is an Extended SQL taglib for AxKit eXtensible Server Pages.

SYNOPSIS

Add the esql: namespace to your XSP < xsp:page > tag:

< xsp:page
language="Perl"
xmlns:xsp="http://apache.org/xsp/core/v1"
xmlns:esql="http://apache.org/xsp/SQL/v2"
>

And add this taglib to AxKit (via httpd.conf or .htaccess):

AxAddXSPTaglib AxKit::XSP::ESQL

This tag library provides extensive support for executing SQL statements from within XSP. This tag library is the same as the Cocoon ESQL taglib.

TAG REFERENCE

Note that below we use the esql: prefix as a convention, however you can use whatever prefix you like provided it is mapped to the appropriate namespace.

< esql:connection>

parent: none

This is the required wrapper element that declares your connection.

< esql:driver>

parent: < esql:connection>

The contents of this element define the DBI driver to be used. For example, Pg, Sybase, Oracle.

You can also add an optional attribute: transactions=no to the driver element, to indicate that this driver does not support transactions (or just that you dont want to use transactions).

< esql:dburl>

parent: < esql:connection>

The name of this tag is a hang-over from the Cocoon (Java) version. In the AxKit version this is simply anything that goes after the driver in the connection string. So for PostgreSQL you might have in here dbname=axkit, to connect to the "axkit" database. The full connect string is constructed as follows:

"dbi:$driver" . ($dburl ? ":$dburl" : "")

See your DBD driver documentation for more details on what is valid for the connection string.

< esql:username>

parent: < esql:connection>

The username to connect to the database with.

< esql:password>

parent: < esql:connection>

The password to use to connect to the database.

< esql:execute-query>

parent: < esql:connection>

This tag is a wrapper tag around queries. You may have as many queries as you like within a single < esql:connection> tag.

< esql:skip-rows>

parent: < esql:execute-query>

The contents of this tag (which may be an < xsp:expr>) define a number of rows to skip forward in the result set.

< esql:max-rows>

parent: < esql:execute-query>

The maximum number of rows to return.

< esql:query>

parent: < esql:execute-query>

The contents of this tag define the query to be executed.

< esql:parameter>

parent: < esql:query>

This tag can be put in your SQL query everywhere you might put a ? in your SQL in DBI. ESQL is intelligent enough to create a cached statement when you do this, and only execute your code when necessary. You put an expression (or another taglib) within the parameter tag (see the example below).

< esql:results>

parent: < esql:execute-query>

The contents of this tag are "executed" whenever the query returns some results.

< esql:row-results>

parent: < esql:results>

The contents of this tag are "executed" for each row of the results

< esql:get-columns>

parent: < esql:row-results>

This tag gets all of the columns in the current row, and outputs them as < column_name>value< /column_name>. If you specify an attribute tag-case="upper", all columns are upper case. Alternatively, "lower" gives you all tags in lower case. An ancestor attribute is also allowed, see "Nested Results" below for more details.
get-*

parent: < esql:row-results>

These are:

get-column
get-string
get-boolean
get-double
get-float
get-int
get-long
get-short
(and more below)

Each of these takes either an attribute column="name", or a child tag, < esql:column> which gives the column name. Alternatively either the attribute or child element can be an integer (starting at 1) specifying the column number.
Also allowed is an ancestor attribute, which is an integer (default 0), which indicates how far up the nested results you go. See Nested Results below.

< esql:get-date>, < esql:get-time>, < esql:get-timestamp>

parent: < esql:row-results>

These tags are the same as get-* above, except they also take a format="..." attribute, which contains a strftime formatting string.

< esql:get-xml>

parent: < esql:row-results>

Again the same as get-* above. This tag assumes the contents of the column are valid XML, and appends that XML into the result tree.

< esql:get-row-position>

parent: < esql:row-results>

Gets the current row number. Optional ancestor attribute.

< esql:get-column-name>

parent: < esql:row-results>

Gets the column name indicated by the numbered column in the column="..." attribute, or the child < esql:column> element. The attribute/child can actually be a string (name), but then what is the point of that?

< esql:get-column-label>

parent: < esql:row-results>

Gets the label of the column. This is a hang-over from the Cocoon java implementation where sadly nobody seems to know what label is compared with name. In this case, get-column-name is always lower case, whereas get-column-label is returned in the case that the DBD driver returns it as.

< esql:get-column-type-name>

parent: < esql:row-results>

Returns the TYPE_NAME of the column indicated as other get-* elements. See the DBI docs for more details.

< esql:no-results>

parent: < esql:execute-query>

The contents of this element are executed when the SQL returned no rows.

< esql:update-results>

parent: < esql:execute-query>

The contents of this element are executed when the SQL was an update statement. The number of rows updated are in the $rv variable.

DBI::FAQ is a Perl module for the Frequently Asked Questions of the Perl5 Database Interface.

What is DBI, DBperl, Oraperl and *perl?

To quote Tim Bunce, the architect and author of DBI:

``DBI is a database access Application Programming Interface (API)
for the Perl Language. The DBI API Specification defines a set
of functions, variables and conventions that provide a consistent
database interface independant of the actual database being used.

In simple language, the DBI interface allows users to access multiple database types transparently. So, if you connecting to an Oracle, Informix, mSQL, Sybase or whatever database, you dont need to know the underlying mechanics of the 3GL layer. The API defined by DBI will work on all these database types.

A similar benefit is gained by the ability to connect to two different databases of different vendor within the one perl script, ie, I want to read data from an Oracle database and insert it back into an Informix database all within one program. The DBI layer allows you to do this simply and powerfully.

DBperl is the old name for the interface specification. Its usually now used to denote perl4 modules on database interfacing, such as, oraperl, isqlperl, ingperl and so on. These interfaces didnt have a standard API and are generally not supported.

Heres a list of DBperl modules, their corresponding DBI counterparts and support information. Please note, the authors listed here generally do not maintain the DBI module for the same database. These email addresses are unverified and should only be used for queries concerning the perl4 modules listed below. DBI driver queries should be directed to the dbi-users mailing list.

However, some DBI modules have DBperl emulation layers, so, DBD::Oracle comes with an Oraperl emulation layer, which allows you to run legacy oraperl scripts without modification. The emulation layer translates the oraperl API calls into DBI calls and executes them through the DBI switch.

Heres a table of emulation layer information:

Module Emulation Layer Status
------ --------------- ------
DBD::Oracle Oraperl Complete
DBD::Informix Isqlperl Under development
DBD::Ingres Ingperl Complete?
DBD::Sybase Sybperl Working? ( Needs verification )
DBD::mSQL Msqlperl Experimentally released with
DBD::mSQL-0.61

The Msqlperl emulation is a special case. Msqlperl is a perl5 driver for mSQL databases, but does not conform to the DBI Specification. Its use is being deprecated in favour of DBD::mSQL. Msqlperl may be downloaded from CPAN via:

http://www.perl.com/cgi-bin/cpan_mod?module=Msqlperl

Anemon Dhcp Servers goal is to create an implementation of the DHCP protocol under GPL and a lot of stuff around to facilitate network management.
The python sqlobject modules gives anemon the ability to use many database as backend (mysql, postgresql, mssql, sqllite, sybase, etc..)
The project is subdivised (at the moment) in 4 components :
- The Anemon Dhcp Server is a Python/SQL implementation of the DHCP server protocol
- The Anemon Web Center is a web management interface to Anemon Dhcp Server and MyDNS
- The Anemon Dhcp Client will be a Python implementation of the DHCP client protocol
- The Anemon Dhcp relay will be a Python implementation of the DHCP relay protocol

SQL Relay is a persistent database connection pooling, proxying and load balancing system for Unix and Linux.
Main features:
SQL Relay is ideal for:
- speeding up database-driven web-based applications
- enhancing the scalability of database-driven web-based applications
- distributing access to replicated databases
- throttling database access
- accessing databases from unsupported platforms
- migrating applications from one database to another
SQL Relay supports the following database backends:
- Oracle
- MySQL
- mSQL
- PostgreSQL
- Sybase
- MS SQL Server
- IBM DB2
- Interbase
- Sybase
- SQLite
- ODBC
- MS Access
The SQL Relay client APIs support advanced database operations such as bind variables, multi-row fetches, client-side result set caching and suspended transactions. SQL Relay has native client APIs for the following languages:
- C
- C++
- Perl
- Python
- PHP
- Ruby
- Java
- TCL
- Zope
SQL Relay provides drivers for the following database abstraction layers:
- Perl DBD
- Python DB
- Ruby DBD
- PHP Pear DB
An application coded using another databases native client API may be able to use SQL Relay without modification. SQL Relay provides drop-in replacement libraries for:
- MySQL
- PostgreSQL
SQL Relay also features:
- command line clients
- a GUI configuration tool
- extensive documentation
Enhancements:
- Several contributed patches were applied.
- Oracle stability was improved.
- Support for Oracle OS-authentication was added.
- The maxlisteners option was added.
- Support for Sybase stored procedures which return result sets was added.
- A Zope empty-result set bug was fixed.
- Support for Mac OS X, Solaris, and Cygwin was improved.