doe300 / jactiverecord Goto Github PK

Create android version of JActiveRecord!

• Which android version?
  Links:
  http://stackoverflow.com/questions/15756230/android-is-jdbc-supported-in-android-devices

Add scopes to unify condition, order and limit into one data-type.
Add to:
FinderMethods:

• findWithScope
• findFirstWithScope
  QueryMethods:
• withScope

Compare to https://github.com/javalite/activejdbc:

• Features
• Performance
• Usability
• Configuration

New features include:

• Java 8 support. Check extension, can be made use of?
• X DevAPI: something about better integration of relational DBs into code. Could be very useful

• Test UUID as column-type (automatic usage, conversion)
• make use of multi-thread support?

Future plans:

• Allow JOIN for conditions, orders and retrieval?
• Improve/Unify type-mapping DB->records and records->DB

For v0.9:

• Improve test coverage. Make sure, every method of a class is covered by the Unit-test for this class
• Implement GraphQL service? (see GraphQL and GraphQL-java)
• ...

For v0.7:

• Add support for PropertyChangeListeners for records (optional) See doe300/jactiverecord-extensions
• Add mechanism to add PropertyChangeListeners to all records of a given type to RecordBase
• Extend RecordHandler to allow for ProxyHandlers to hok into the attribute getters/setters
• Add Order to RecordSet and to #getForCondition()
• Extend Order with support for scalar functions
• Add table sharding to RecordBase

For v0.6:

• Unify Migrations for SQL and no-SQL RecordStores
• Add some common SQL scalar functions
• Add scalar functions to Conditions (and maybe selection-columns)
• Reorganize SQL-functions

For v0.5:

• Add aggregation-functions to RecordBase and RecordSet
• Create driver for each SQL-dialect to improve compatibility
• Improve and unifiy Java-to-SQL and SQL-to-Java type-mappings
• Improve compatibility with currently tested SQL-dialects

For v0.4:

• ValidationGenerator: generate validation-methods from annotations
• AssociationGenerator: generate association-methods from annotations. Get/Set for has-one/belongs-to and getAll/add/remove for has-many/has-many-through
• Improve checking annotation-processors (custom methods, i.e. for converter/validation)