perl
< html
< web
< programming
< Computing
< alligin
Get flash to fully experience Pearltrees
Unless you need the Net::Z3950 API for backwards compatibility (i.e. you're building it because it's a prerequisite for an existing application) you should instead use the newer and better ZOOM-Perl module . Its functionality is a strict superset of this module's, but it provides many additional features, including record-format translation, character-set handling and a properly documented asynchronous API. Because it is based on ZOOM-C, the ZOOM-Perl model inherits functionality from that module, and will continue to benefit from its further development. Finally, the ZOOM-C dependency allows the ZOOM-Perl code to be much shorter than Net::Z3950 , and therefore easier to support: ``The cheapest, fastest, most reliable components of a computer system are those that are not there'' -- Gordon Bell. The Net::Z3950 module provides a Perl interface to the Z39.50 information retrieval protocol (aka.
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
The RPM packages are signed with gpg. You can download my gpg key with the ID 0.7.50CD6D from every public keyserver like: http://wwwkeys.de.pgp.net/
SQL::Translator is a group of Perl modules that manipulate structured data definitions (mostly database schemas) in interesting ways, such as converting among different dialects of CREATE syntax (e.g., MySQL-to-Oracle), visualizations of schemas (pseudo-ER diagrams: GraphViz or GD ), automatic code generation (using Class::DBI ), converting non-RDBMS files to SQL schemas (xSV text files, Excel spreadsheets), serializing parsed schemas (via Storable, YAML and XML), creating documentation (HTML and POD), and more. New to version 0.03 is the ability to talk directly to a database through DBI to query for the structures of several databases. Through the separation of the code into parsers and producers with an object model in between, it's possible to combine any parser with any producer, to plug in custom parsers or producers, or to manipulate the parsed data via the built-in object model.