Free import excel mysql software for linux

DateTime::Format::Excel is a Perl module that can convert between DateTime and Excel dates.

SYNOPSIS

use DateTime::Format::Excel;

# From Excel via class method:

my $datetime = DateTime::Format::Excel->parse_datetime( 37680 );
print $datetime->ymd(.); # 2003.02.28

# or via an object

my $excel = DateTime::Format::Excel->new();
print $excel->parse_datetime( 25569 )->ymd; # 1970-01-01

# Back to Excel number:

use DateTime;
my $dt = DateTime->new( year => 1979, month => 7, day => 16 );
my $daynum = DateTime::Format::Excel->format_datetime( $dt );
print $daynum; # 29052

# or via an object
my $other_daynum = $excel->format_datetime( $dt );
print $other_daynum; # 29052

Excel uses a different system for its dates than most Unix programs. This module allows you to convert between a few of the Excel raw formats and DateTime objects, which can then be further converted via any of the other DateTime::Format::* modules, or just with DateTimes methods.

If you happen to be dealing with dates between 1 Jan 1900 and 1 Mar 1900 please read the notes on epochs.

If youre wanting to handle actual spreadsheet files, you may find Spreadsheet::WriteExcel and Spreadsheet::ParseExcel of use.

Java::Import::Examples is an example of how to use Java::Import to call into Java classes.

Making RMI calls from Perl

One nice thing about Java is the extremely straight forward manner in which it allows you to make calls to remote objects residing on distant servers. Many people use this ability as a point of integration between their system and a posible third party or legacy system. Unfortunatly, for the most part the ability to make calls to these remote objects is something that only other Java applications can do without making a big fuss about it. However, we can now do this from Perl.

Assume that I have a RMI server from which I can get data from in the form of simple Java Beans. One method of doing this is to use the GCJ::Cni library and natively compile and wrap a set of Java Classes which can then be used from my Perl script. However, there is an easier way.

Lets begin by descriping the Java interfaces that well be working with. We first have the Remote Interface that we will be interacting with:

import java.rmi.*;
public interface RemoteInterface extends Remote {
public SomeBean getMessage(String seedMessage) throws RemoteException;
}
And we also have the bean we will be asking for:
import java.io.*;
public class SomeBean implements Serializable {
private String value;
public SomeBean() {}
public void setValue ( String _value ) { ... }
public String getValue ( ) { ... }
}
As far as any Perl client program is concerned this is all we need to know about.
Now all there is left to do is write a client:
use Java::Import qw(
java.rmi.Naming
);

my $remote_interface = java::rmi::Naming->lookup(jstring("//localhost/Home"));
my $bean = $remote_interface->getMessage(jstring("Hi there"));
print $bean->getValue(), "n";

Thats all there is. Notice that all we had to tell Java::Import about was java.rmi.Naming, this is because it was the only class we used by name in our Perl code, every other Java class (the objects held by $bean and $remote_interface) was returned by some other method call originating from java.rmi.Naming.

In order to run this example we have to make sure everything is in its place. We start by compiling the client code. Assuming that we have been given a Stub class file (RemoteObject_Stub.class) we can do the following:

gcj -C SomeBean.java RemoteInterface.java
fastjar -cvf client.jar SomeBean.class RemoteInterface.class RemoteObject_Stub.class

Making sure our server is reachable we can then run the client code:

CLASSPATH=client.jar perl client.pl

Thats it, you should then see the message returned by your server.

XML::Excel is a Perl extension converting Excel files to XML.

SYNOPSIS

use XML::Excel;
$excel_obj = XML::Excel->new();
$excel_obj = XML::Excel->new(%attr);

$status = $excel_obj->parse_doc(file_name);
$status = $excel_obj->parse_doc(file_name, %attr);

$excel_obj->declare_xml(%attr);
$excel_obj->declare_doctype(%attr);

$excel_obj->print_xml(file_name, %attr);

XML::Excel is a new module which is going to be upgraded very often as my time permits. For the time being it uses Spreadsheet::ParseExcel module object default values to parse the (*.xls) document and then creates a perl data structure with xml tags names and data. At this point it does not allow for a write as you parse interface but is the first upgrade for the next release. I will also allow more access to the data structures and more documentation.

I will also put in more support for XML, since currently it only allows a simple XML structure. Currently you can modify the tag structure to allow for attributes. No DTD support is currently available, but will be implemented in a soon coming release. As the module will provide both: object and event interfaces, it will be used upon individual needs, system resources, and required performance. Ofcourse the DOM implementation takes up more resources and in some instances timing, its the easiest to use.

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

SYNOPSIS

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

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

### allocate a persistent object ###
my $emp = new Persistent::MySQL($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 MySQL 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.

Netacct-mysql is modified version of traffic accounting daemon net-acct which stores collected data in MySQL. It supports writing accounting information in a single line in MySQL per day for every IP (mrta style).
Netacct functions by analogy with sniffer, i.e. it keeps track of all the traffic passing through the network interfaces assigned by the configuration file. Data are stored in the memory and periodically saved in the database. The default data save period is 300 seconds (see option "flush" in the config file).
The application is used for accounting of the network traffic passed through your router/gateway. It is based on the libpcap library and functions as a userspace daemon. Options for dividing the network traffic into 4 categories:
- international
- peering
- direct
- local
The traffic accounts are saved in a database, and for the time being MySQL and Oracle are supported. As libpcap is used for gathering the network data the application runs (for the moment) on the following operating systems:
- Linux
- FreeBSD
- OpenBSD
- Solaris
For more detailed information regarding a particular OS, please read the FAQ file.
Enhancements:
- netacct.h:
- process.c:
- naccttab.sample:
- fixed disable fields in config file, now it works does not write some fields in dump file - fixed

JDatabaseImport is a simple tool created to import data between different databases.
How does it work?
You can work with it in two ways, either using a configuration file or accessing its api using Java.
Example:
The following code show an example of a file called *export.xml*:
< export >
< from >
< driver >org.hsqldb.jdbcDriver< / driver >
< url >jdbc:hsqldb:hsql://localhost/source< / url >
< username >sa< / username >
< password >mysapass< / password >
< / from >
< to >
< driver >com.mysql.jdbc.Driver< / driver >
< url >jdbc:mysql://localhost/target< / url >
< username >root< / username >
< password >myrootpass< / password >
< / to >
< table name="firstTable"/ >
< table name="secondTable" >
< ignore >fieldToBeIgnored< / ignore >
< / table >
< table name="thirdTable"/ >
< / export >
Note that JDatabaseImport *will not* generate the target tables, but only import data from one source into the other.
In order to run JDatabaseImport, you need to put all drivers in the classpath and run it. The following code is an example on how to use it to import from mysql to hsqldb
java -cp mysql-connector-3.1.1.jar:hsqldb.jar:jdatabaseimport.jar br.com.caelum.jdatabaseimport.Main export.xml
Enhancements:
- This initial release has been tested with hsqldb, MySQL, Derby, and Oracle using some field types and different configurations.

ProM Import Framework project allows you to extract process enactment event logs from a set of information systems.
These can be exported in the MXML format, which is the standard event log data format for Process Mining analysis techniques.
Process Mining is a family of a-posteriori analysis techniques to extract abstract information from process enactment logs. More in-depth information about the are of process mining is available at processmining.org.
Installation:
- Decompress and extract the provided *.tar.gz archive.
- This will create a folder ProMimport, containing all files necessary.
- Start the application by running the provided shell script start.sh.
- The import filter plugins delivered with your installation package are located in the Plugins folder inside the ProMimport directory.
- Load the plugins (which are packaged in *.jar files) that you want to use from within the running app. For that, use Load filter plugin.. from the Filters menu.
- 3rd party plugins, or plugins developed by you, can be added to the application in exactly the same manner.
- Once imported, filters are automatically added to the applications filter cache, and zre re-loaded on every successive startup. Further, all filter and application configuration data is transparently made persistent by the application.
- Thus, after importing all filter plugins necessary, you can safely delete the Plugins folder.
Enhancements:
- This is the initial release of the ProM framework under the new open source CPL license.
- Installers / disk images are provided for Windows and Mac OS X, while the provided source archive is also executable on all platforms supporting Java 5.0.
- Notice that this release depends on a Java runtime environment of version 1.5 / 5.0 or later.
- Prior JRE releases may yield unexpected errors.