BibSonomy ::  user :: gresch ::

SQLRunner is a simple JDBC Client which helps Java developers with various methods. You can build, test and run select, update and DML statements (also callable statements with out put parameters) and export or import data in/from csv-files or XML-fi

AutoPatch was born from the needs of using an agile development process while working on systems that have persistent storage. Without AutoPatch, developers usually can't afford the maintenance headache of their own database, and DBAs are required just to apply changes to all of the various environments a serious development effort requires. The very application of database changes becomes an inefficient, error-prone, expensive process, all conspiring to discourage any refactoring that touches the model, or being a bottleneck when model changes are made. AutoPatch solves this problem, completely. With AutoPatch, an agile development process that requires a database change looks like this: * Developer alters the model, which requires a change to the database * Developer possibly consults a DBA, and develops a SQL patch against their personal database that implements the alteration * Developer commits the patch to source control at the same time as they commit their dependent code * Other developers' and environments' databases are automatically updated by AutoPatch the next time the new source is run This represents streamlined environment maintenance, allowing developers to cheaply have their own databases and all databases to stay in synch with massively lower costs and no environment skew. That's what AutoPatch does. Clusters with one database? Multiple schemas? Logical migrations, instead of just DDL changes? Need to do something special/custom? Need to distribute your changes commercially? All without paying anything? No problem.

In many Java EE applications declarative security is required where user and group information is stored in a database. To support this, an application server must support a security realm based on a JDBC datasource. Glassfish V2 application server also supports a configuration like this through the JDBCRealm. Unfortunately, this JDBCRealm is restrictive in various ways: * It assumes a data model where groups are modeled as value objects in the sense of Eric Evan's terminology in Domain Driven Design. Specifically, if a group should have more properties apart from its name, then this should be modeled in a different database structure with the group name as a key. * A very specific datamodel is assumed. Two tables are used: One with for every user the encoded password and another with pairs of usernames and groupnames to define to which groups a user belongs. * It is static in that it assumes that a user will always be a part of the same groups over time. After retrieving the groups for the first time, it caches them indefinitely. This makes the JDBCRealm of glassfish unsuitable for dynamic applications where users can join or leave groups. As is clear, the JDBCRealm of glassfish either fits your purpose and you are done, or it doesn't and you have to either work around it in your application or create a separate more flexible JDBC security realm yourself. Since I had a stable application that I wasn't intending on modifying, I decided to do the latter. The FlexibleJdbcRealm is a JDBC security realm which is similar to the approach used in JBoss application server. Instead of depending on a fixed database structure with only limited configuration, it is configured with two queries instead: * One query for determining the (encoded) password of the user based on the user name. * One query for determining the groups the user belongs to based on the user name. In other words, instead of assuming a certain type of data model with configuration of some column and table names and constructing the two JDBC queries for passwords and groups as JDBCRealm does, the FlexibleJDBCRealm is configured with the two queries. As a result, FlexiblJDBCRealm is more general than JDBCRealm since it can handle any datamodel that JDBCRealm can. In particular, in the application that triggered this, I had a datamodel that did not fit the one assumed by JDBCRealm. In my design I am using surrogate keys and have three tables: * a Users table with primary key, user name, encoded password, and other user attributes * a groups table with primary key, group name, and other group attributes * a user_groups table with a mapping of users to groups (based on primary key) This datamodel can easily be handled using FlexibleJdbcRealm but would have required a redesign of the application if I would have used JDBCRealm.

Teiid is a data virtualization system that allows applications to use data from multiple, heterogenous data stores. Teiid is comprised of tools, components and services for creating and executing bi-directional data services. Through abstraction and federation, data is accessed and integrated in real-time across distributed data sources without copying or otherwise moving data from its system of record.

CsvJdbc is a simple read-only JDBC driver that uses Comma Separated Value (CSV) files as database tables. It is ideal for writing data importing programs.

The Envers project aims to enable easy versioning of persistent JPA classes. All that you have to do is annotate your persistent class or some of its properties, that you want to version, with @Versioned. For each versioned entity, a table will be created, which will hold the history of changes made to the entity. You can then retrieve and query historical data without much effort. Similarly to Subversion, the library has a concept of revisions. Basically, one transaction commit is one revision (unless the transaction didn't modify any versioned entities). As the revisions are global, having a revision number, you can query for various entities at that revision, retrieving a (partial) view of the database at that revision.

JUDIE steht für Java Universal Database Import and Export. Das Tool exportiert einzelne oder alle Tabellen einer JDBC Datenbank nach XML und importiert diese wieder in andere Datenbanken. Es ist als API (JAR), Kommandozeilenprogramm oder Eclipse Plugin verfügbar. Es kann für Entwickler und Administratoren nützlich sein, um Daten zwischen Datenbanken zu übertragen, besonders zum Aufsetzen von Testdatenbanken. Wegen der einfachen API kann das auch automatisiert werden, z.B. als Skript oder Ant-Task.

jLynx is a simple, lite, hi-performance layer over the JDBC API. Persist and retrieve POJO and Map objects directly. Designed for developer productivity. Simpler, easy to learn, easy to configure as compared to Hibernate, JPA, etc. jLynx generates JavaBean objects based on your database schema. For example if you have 24 tables and views in your database, jLynx will create 24 objects with properties that map to the field names in each table. The jLynx Generator creates the objects and compiles them. You can also use the generated source instead if you prefer to customize the objects. Using the API to persist objects is trivial. jLynx Framework implements the Relational interface, which has all necessary methods to persist objects and fetch entire collections of objects. jLynx leverages the strengths of SQL and the strengths of Java without having to write/maintain J2EE code. It is truly the best of both worlds.

Hibernate Synchronizer is a free Eclipse plugin code generation tool to be used with the Hibernate persistence framework. The plugin will automatically generate java code when your hibernate mapping files are modified. Objects are created with generated code in an abstract base class and a user-modifiable extension class so user code does not get deleted when the generation is performed. The automaticallly generated objects include: * Value Objects * Proxy Interfaces * Composite Key Objects * Enumeration Objects * Component Objects * Subclasses * DAOs Other features include: * Editor with code assist and outline view * Custom template generation * New mapping file wizard that queries your database * New configuration file wizard * Actions for adding mapping references, synchronizing files, and manually activating code generation

DB Schema Viewer is an Eclipse plugin that builds a graphical view of an existing database. Reverse Engineering is performed through JDBC. The most popular databases are currently supported: * MySQL * PostgreSQL * Firebird

Eclipse SQL Explorer is a thin SQL client that allows you to query and browse any JDBC compliant database. It supports plugins with specialized functionality for individual databases (Oracle, DB2 and MySQL) and can be extended to include specialized support for other databases.

This article presents with an solution on how to page through large amountsofdata effectively without taking down your database and without keeping it all in memory.

Jackcess is a pure Java library for reading from and writing to MS Access databases. It is not an application. There is no GUI. It's a library, intended for other developers to use to build Java applications. Jackcess is licensed under the GNU Lesser General Public License. Take a look at our Frequently Asked Questions for more info.

The JDBC Importer provides a consistent mechanism of importing data from files into a JDBC compliant database. Currently, each database vendor has their own utility or command that must be learned. Additionally, there are some limitations and caveats abou