Software History for BeanKeeper

Revision: 20

Changed by Sysop, 8 months, 1 week ago

• Added public with value True

Revision: 19

Changed by Sysop, 8 months, 1 week ago

• Changed download_page: from http://sourceforge.net/project/showfiles.php?group_id=211409 to http://beankeeper.netmind.hu/download.php

Revision: 18

Changed by Sysop, 8 months, 1 week ago

• Changed downloads to:
  1. Web : http://beankeeper.netmind.hu/download/beankeeper-2.6.0.tar.gz

Revision: 17

Changed by Sysop, 8 months, 1 week ago

• Added to platforms: Web

Revision: 16

Changed by Sysop, 8 months, 1 week ago

• Added documents_tutorial with value http://beankeeper.netmind.hu/tutorial.php

Revision: 15

Changed by Sysop, 8 months, 1 week ago

• Added documents with value http://beankeeper.netmind.hu/doc/beankeeper_toc.html

Revision: 14

Changed by Sysop, 8 months, 1 week ago

• Added to features:
  1. Simple to use.
  2. Zero configuration.
  3. Small footprint.
  4. Supports PostgreSQL,MySQL,HSQLDB,Oracle.
  5. Full polymorphism support!
  6. Simple, readable, easy query language.
  7. Handles relations expressed with Lists, Maps, Sets, Collections.
  8. Handles references to other objects, self-references, circular references.
  9. Lazy loading of objects loads objects only when needed, and only so much what is needed (paging).
  10. Historical search capability (select objects at a given date).
  11. "View" selection from multiple objects (scalar query).
  12. Result list cache.
  13. Distributed, scalable operation!
  14. Hierarchical/polymorphic locking (lock classes to lock all instances of that class or any subclass).

Revision: 13

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Scalar query support enables view-centric, more efficient data recall.

Revision: 12

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Relations like references to other objects, Lists, Maps, Sets, Collections are handled 100% transparently by the library.

Revision: 11

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Large result sets are automatically paged! Paging is 100% transparent, so a million-record result list can be given directly to the presentation layer, without caring for memory usage and database load!

Revision: 10

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Transactions are always 'serializable'. Meaning: during a transaction nothing can influence the result of queries from outside the transaction. This means running the same query twice inside a transaction (no matter how long the transaction takes) will always produce the exact same result, except only if the result was modified between the to queries in the same transaction.

Revision: 9

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Full (transparent) polymorphism support ensures that (most of the time) the library does not get in the way of the programmer. The model is persisted just in the way the programmer expressed through inheritence, and is recalled with all the attributes of polymorphism.

Revision: 8

Changed by Sysop, 8 months, 1 week ago

• Removed from features: A custom, object oriented query language ensures, that no complicated SQL needs to be written.

Revision: 7

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Real portability between databases. BeanKeeper hides all database specific behaviour from the programmer, like: null value handling, empty strings (oracle), case sensitive and insensitive searches, reserved names, etc. That means, one can switch between database implementations, and can assume that (with the exception of a few documented cases) the software build upon the library will continue to work.

Revision: 6

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Scalability. The library is capable of distributed operation, from virtually unlimited nodes.

Revision: 5

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Zero-configuration. Nothing needs to be configured, only the database url is needed for the library to initialize.

Revision: 4

Changed by Sysop, 8 months, 1 week ago

• Removed from features: Simple usage, which is possible with learning only 3 methods, and reading the tutorial.

Revision: 3

Changed by Sysop, 8 months, 1 week ago

• Changed description: BeanKeeper is a full featured, powerful object/relational persistence and query library for Java. BeanKeeper offers the following key features: * Simple usage, which is possible with learning only 3 methods, and reading the tutorial. * Zero-configuration. Nothing needs to be configured, only the database url is needed for the library to initialize. * Scalability. The library is capable of distributed operation, from virtually unlimited nodes. * Relations like references to other objects, Lists, Maps, Sets, Collections are handled 100% transparently by the library. * Large result sets are automatically paged! Paging is 100% transparent, so a million-record result list can be given directly to the presentation layer, without caring for memory usage and database load! * Transactions are always 'serializable'. Meaning: during a transaction nothing can influence the result of queries from outside the transaction. This means running the same query twice inside a transaction (no matter how long the transaction takes) will always produce the exact same result, except only if the result was modified between the to queries in the same transaction. * Full (transparent) polymorphism support ensures that (most of the time) the library does not get in the way of the programmer. The model is persisted just in the way the programmer expressed through inheritence, and is recalled with all the attributes of polymorphism. * A custom, object oriented query language ensures, that no complicated SQL needs to be written. * Scalar query support enables view-centric, more efficient data recall. * Real portability between databases. BeanKeeper hides all database specific behaviour from the programmer, like: null value handling, empty strings (oracle), case sensitive and insensitive searches, reserved names, etc. That means, one can switch between database implementations, and can assume that (with the exception of a few documented cases) the software build upon the library will continue to work.

Revision: 2

Changed by Sysop, 8 months, 1 week ago

• Changed description: BeanKeeper is a full featured, powerfuloffers the following key features: * Simple usage, which is possible with learning only 3 methods, and reading the tutorial. * Zero-configuration. Nothing needs to be configured, only the database url is needed for the library to initialize. * Scalability. The library is capable of distributed operation, from virtually unlimited nodes. * Relations like references to other object/relational persistence ands, Lists, Maps, Sets, Collections are handled 100% transparently by the library. * Large result sets are automatically paged! Paging is 100% transparent, so a million-record result list can be given directly to the presentation layer, without caring for memory usage and database load! * Transactions are always 'serializable'. Meaning: during a transaction nothing can influence the result of query library for Jaies from outside the transaction. This means running the same query twice inside a transaction (no matter how long the transaction takes) will always produce the exact same result, except only if the result was modified between the to queries in the same transaction. * Full (transparent) polymorphism support ensures that (most of the time) the library does not get in the way of the programmer. The model is persisted just in the way the programmer expressed through inheritence, and is recalled with all the attributes of polymorphism. * A custom, object oriented query language ensures, that no complicated SQL needs to be written. * Scalar query support enables vaiew-centric, more efficient data recall. * Real portability between databases. BeanKeeper hides all database specific behaviour from the programmer, like: null value handling, empty strings (oracle), case sensitive and insensitive searches, reserved names, etc. That means, one can switch between database implementations, and can assume that (with the exception of a few documented cases) the software build upon the library will continue to work.

Revision: 1

Changed by Sysop, 8 months, 1 week ago

• Added to features:
  1. Simple usage, which is possible with learning only 3 methods, and reading the tutorial.
  2. Zero-configuration. Nothing needs to be configured, only the database url is needed for the library to initialize.
  3. Scalability. The library is capable of distributed operation, from virtually unlimited nodes.
  4. Relations like references to other objects, Lists, Maps, Sets, Collections are handled 100% transparently by the library.
  5. Large result sets are automatically paged! Paging is 100% transparent, so a million-record result list can be given directly to the presentation layer, without caring for memory usage and database load!
  6. Transactions are always 'serializable'. Meaning: during a transaction nothing can influence the result of queries from outside the transaction. This means running the same query twice inside a transaction (no matter how long the transaction takes) will always produce the exact same result, except only if the result was modified between the to queries in the same transaction.
  7. Full (transparent) polymorphism support ensures that (most of the time) the library does not get in the way of the programmer. The model is persisted just in the way the programmer expressed through inheritence, and is recalled with all the attributes of polymorphism.
  8. A custom, object oriented query language ensures, that no complicated SQL needs to be written.
  9. Scalar query support enables view-centric, more efficient data recall.
  10. Real portability between databases. BeanKeeper hides all database specific behaviour from the programmer, like: null value handling, empty strings (oracle), case sensitive and insensitive searches, reserved names, etc. That means, one can switch between database implementations, and can assume that (with the exception of a few documented cases) the software build upon the library will continue to work.
• Added shortdesc with value BeanKeeper is a full featured, powerful object/relational persistence and query library for Java.