Free transactional leadership software for mac

Oracle Berkeley DB Java Edition is a high performance, transactional storage engine written entirely in Java. Like the highly successful Berkeley DB product, Berkeley DB Java Edition executes in the address space of the application, without the overhead of client/server communication.
It stores data in the applications native format, so no runtime data translation is required. Berkeley DB Java Edition supports full ACID transactions and recovery. It provides an easy-to-use, programmatic interface, allowing developers to store and retrieve information quickly, simply and reliably.

Main features:
- Local, in-process data storage.
- Schema-neutral, application native data storage.
- Keyed and sequential data retrieval.
- Easy-to-use Java Collections API.
- Persistence API for accessing Java objects.
- Single process, multi-threading model.
- Record level locking for high concurrency.
- Support for secondary indexes.
- In-memory, on disk or both.
- Configurable background cleaner threads re-organize data and optimize disk use.
- Full ACID compliance.
- Selectable isolation levels and durability guarantees, configurable on a per-transaction basis.
- Managed transactions using the Java Transaction API (JTA).
- J2EE application server integration using J2EE Connector Architecture(JCA).
- Provides support for monitoring, auditing and administration using the Java Management Extensions (JMX).
- Catastrophic and routine failure recovery modes.
- Timeout based deadlock detection.
- Hot and cold backups, log file compaction, and full database dumps.
- 100% pure Java for portability and ease of development.
- Single JAR file - easy to install, runs in the same JVM as the application.
- Java 1.4.2 or later Standard Edition JVM required.
- Programmatic administration and management-zero human administration.
- API for routine administrative functions.
- Small footprint 772KB.
- Scalable to terabytes of data, millions of records.
- Source code, test suite included.

System requirements:
-

Enhancements
- Fix a bug that somtimes causes two log cleaner threads (when multiple threads are configured or multiple app threads call Environment.cleanLog) to select the same file to clean. This can result in two attempts to delete the log file after cleaning. The second attempt causes an exception to be traced repeatedly, but no other side effect. The problem is transient and goes away if the Environment is closed and re-opened. An example of the exception is below. The symptom is that this exception occurs repeatedly, and the file is not present.
- Fix a bug that could cause a LogFileNotFoundException when using an XAEnvironment, if a prepared transaction is not ended prior to a crash and then the prepared transaction is aborted after recovering from a crash. [#17022] (3.3.79)
- Fix a bug that prevented deferred-write record deletions from being made durable by Database.sync, if a crash occurs after Database.sync but prior to the next checkpoint. Under rare circumstances this could also result in a LogFileNotFoundException later when accessing the deleted entry. [#16864] (3.3.78)
- Fix a bug that prevents log cleaning from functioning properly when a temporary DB (DatabaseConfig.setTemporary) is large enough to overflow the JE cache. Also fix a bug that could in rare cirumstances cause an endless loop while performing log cleaning. [#16928] (3.3.78)
- Fix a bug that caused an infinite loop under certain timing dependent circumstances when using EnvironmentConfig.setSharedCache(true). This bug was reported in two different forum posts. Thanks to Kevin Jackson and Vyacheslav Lukianov for reporting it! [#16882] (3.3.78)
- Improve output of partial information in DatabaseEntry.toString. Thanks to archie172 for reporting this on OTN. [#16929] (3.3.78)
- Fix a bug in SecondaryCursor.dup that required the cursor to be initialized. This method, like Cursor.dup, may now be called whether the cursor is initialized or not. Thanks to archie172 for reporting this on OTN. [#16930] (3.3.78)
- Fix a bug that caused NullPointerException when opening an XAEnvironment under certain circumstances, when prepared but uncommitted transactions are present in the JE log and must be replayed during recovery. This bug was reported on the OTN forum by Matthieu Bentot -- thank you Matthieu! An example of the stack trace is below.
- Fix a bug that caused LogFileNotFoundException in rare circumstances for an Environment having one or more Databases configured for duplicates (or one or more SecondaryIndexes with MANY_TO_XXX relationships). The bug only occurs when a single secondary/duplicate key value is associated with a large number of records/entities; specifically, the sub-Btree for a single duplicate key value must have at least 3 levels. [#16712] (3.3.76)
- Fix a bug that caused BufferOverflowException while writing transactional records. This could occur if multiple threads were writing to an environment while using the same Transaction. [#17204]
- Direct Persistence Layer (DPL), Collections and Bind packages - Fix a bug that causes the EvolveStats returned by EntityStore.evolve to contain zeros, even when entities are evolved and written, when no EvolveListener is configured. Thanks to jhalex on OTN for reporting this. [#17024] (3.3.78)

PostgreSQL Database Server 8.3.0 is a program functioning as an open source relational database system. It has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. It runs on all major operating systems, including Linux, UNIX (AIX, BSD, HP-UX, SGI IRIX, Mac OS X, Solaris, SunOS, Tru64), BeOS, and Windows. PostgreSQL Database server already embedded a useful GUI - PGadmin. If you want to import MS Access or other formats to PostgreSQL, you can install a Mac OS X GUI Navicat PostgreSQL

PostgreSQL is an open-source descendant of this original Berkeley code. Also, PostgreSQL can be extended by the user in many ways.

It supports a large part of the SQL:2003 standard and offers many modern features:

1. Complex queries
2. Foreign keys
3. Triggers
4. Views
5. Transactional integrity
6. Multiversion concurrency control

PostgreSQL Database Server for Mac OS X 8.1.4 offers a simple and effective relational database system. It has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. It runs on all major operating systems, including Linux, UNIX (AIX, BSD, HP-UX, SGI IRIX, Mac OS X, Solaris, SunOS, Tru64), BeOS, and Windows. If you need a PostgreSQL Database GUI, you can download NAVICAT PostgreSQL GUI.

It supports to import CSV, XML or other formats to PostgreSQL. PostgreSQL is an open-source descendant of this original Berkeley code. It supports a large part of the SQL: 2003 standard and offers many modern features: complex queries, foreign keys, triggers, views, transactional integrity, and multi-version concurrency control. Also, PostgreSQL can be extended by the user in many ways.

Enhancements: May include unspecified updates, enhancements, or bug fixes.

Onepoint Project integrates project planning, monitoring, progress tracking, controlling and reporting into a single, easy-to-use tool.
Onepoint Project represents a new class of Project Leadership Software solutions that does not require you to compromise between ease-of-use and functionality. In addition, Onepoints different editions scale with your needs and the size of your business.
Global competition, changing customer requirements and short development cycles make it increasingly harder for companies of all sizes to be permanently successful.
Especially the management of time and resource critical development and deployment projects provides ever new challenges for the people in charge. For this, outdated or not integrated project management systems are either not capable of delivering decision relevant information, or at least not fast enough.
Onepoint Project integrates project planning, project controlling, monitoring and reporting into a single, easy to use and open project leadership solution providing you with all relevant information when and where you need it.
There are two Onepoint Project "flavors": Basic (single-user desktop app) and Open (multi-user Web 2.0 app). Basic Edition is targeted at the "rookie" solo project manager and the Open Edition is 100% Web-based and targeted at startups and small project teams.

Main features:
- Reduced project risks through integrated solution and high usability
- Minimized project management effort via project templates and team orientation
- Increased project transparency through ad-hoc monitoring, traffic light functions & plan-actual comparisons
- Significantly minimized costs via reduced risks and administration, but increased transparency

Enhancements
- Together with a major user interface "facelift" we added many practical usability enhancements including more easy to read edit tool buttons, improved visualization of the project detail context (name and description) and extended navigation between project overviews and details.
- Week-based Work Slips Milestone Trends
- Based on feedback from many existing and prospective users we totally redesigned our work slips. Actual time and costs can still be entered on a daily basis, but the visualization of the work slips has been changed to a week-based view speeding up data entry and improving overall usability.
- Issue Tracking Option * Issue Tracking
- The Issue Tracking Option allows to report, track and manage project-related issues directly within Onepoint Project. Issues can be prioritized and support simple escalation scenarios. Like ad hoc tasks, issues are shown in personal task lists and support tracking of time and costs.
- Project Traffic Light Traffic Light
- All multi-project overviews now feature a simple, but powerful project traffic light. The status of the traffic light can be set by the project manager and indicates the internal overall status of the project. In addition, the project status color is visualized in the multi-project schedule.
- Custom Report Wizard Report Wizard
- The new report wizard allows manager users of Onepoint Project to create their own tabular reports simply via point & click. Such custom reports can then be saved and shared with other users or groups within the project organization. Custom reports support grouping, sorting and filtering.
- Risk Management Option * Risk Management
- The Risk Management Option provides the project manager with the ability to manage a version-controlled risk matrix for each project including risk description, probability and impact. Optionally, global risk categories can be defined in order to m

A graph (mathematical lingo for a network) is a flexible data structure that allows a more agile and rapid style of development. You can think of Neo4j as a high-performance graph engine with all the features of a mature and robust database. The programmer works with an object-oriented, flexible network structure rather than with strict and static tables yet enjoys all the benefits of a fully transactional, enterprise-strength database.

In addition, Neo4j includes the usual database features: ACID transactions, concurrency control, transaction recovery, durable persistence, and everything else you would expect from an enterprise-strength database.

Major Features:

1. An intuitive graph-oriented model for data representation. Instead of static and rigid tables, rows and columns, you work with a flexible graph network consisting of nodes, relationships and properties.
2. Adisk-based, native storage manager completely optimized for storing graph structures for maximum performance and scalability.
3. Massive scalability. Neo4j can handle graphs of several billion nodes/relationships/properties on a single machine and can be shared to scale out across multiple machines.
4. A powerful traversal framework for high-speed traversals in the node space.
5. A small footprint. Neo4j is a single

Enhancements:

• API: Removed a number of deprecated methods (primarily for relationship type management) from EmbeddedNeas per warning in the previous release.
• API: Transaction is now an interface.
• API: TraversalPosition now has an isStartNode() method.
• API: NotFound and NotInTransaction runtime exceptions have been moved from internal impl package the api package.
• API: getRelationshipById is now exposed in NeoService.
• API: A common base interface for Node and Relationship has been added that contains the set/get/remove property operations.
• Core: Made it easy embed Neo4j in a Spring application. Spring can be configured to use Neo4js transaction manager.
• Core: All known bugs have been fixed.
• Core: Removed singletons and made everything IoC.
• Core: Lots of minor optimization and improvements above native store layer (nioneo).
• Core: Cleanup of code (removed non used code) and improved exception handling.
• Core: Improved read performance and parallelism by implementing MVCC-like features. Nlocks are now taken during read-only operations, instead concurrent operations are working against snapshot versions.