This is a free and a great SQLite database manager. It also manages the Android SQLite database easily.
SQLite Expert Personal
http://www.sqliteexpert.com/
terça-feira, 6 de dezembro de 2011
segunda-feira, 5 de dezembro de 2011
JBoss Envers and Temporal Databases
It can be used in need of Temporal Databases[1]... It is a great option for historic data!
Envers: Easy Entity Auditing
"The Envers project aims to enable easy auditing/versioning of persistent classes. All that you have to do is annotate your persistent class or some of its properties, that you want to audit, with @Audited. For each audited 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." [2]
[1] http://en.wikipedia.org/wiki/Temporal_database
[2] http://www.jboss.org/envers
Envers: Easy Entity Auditing
"The Envers project aims to enable easy auditing/versioning of persistent classes. All that you have to do is annotate your persistent class or some of its properties, that you want to audit, with @Audited. For each audited 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." [2]
[1] http://en.wikipedia.org/wiki/Temporal_database
[2] http://www.jboss.org/envers
Marcadores:
Hibernate,
Java,
ORM,
Temporal Databases
Hibernate - the best choice
Ok, Hibernate [1] is the best choice for design applications!
"Hibernate is best used to leverage end-to-end OR mapping. It provides a complete ORM solution, but leaves you no control over queries. Hibernate is an ideal solution for situations where you have complete control over both the application and the database design. In such cases you may modify the application to suit the database, or vice versa. In these cases you could use Hibernate to build a fully object-relational application. Hibernate is the best option for object-oriented programmers who are less familiar with SQL." [2]
[1] Hibernate Documentation
http://www.hibernate.org/docs
[2] Comparison of iBatis, Hibernate and JPA
http://www.narendranaidu.com/2008/07/comparison-of-ibatis-hibernate-and-jpa.html
"Hibernate is best used to leverage end-to-end OR mapping. It provides a complete ORM solution, but leaves you no control over queries. Hibernate is an ideal solution for situations where you have complete control over both the application and the database design. In such cases you may modify the application to suit the database, or vice versa. In these cases you could use Hibernate to build a fully object-relational application. Hibernate is the best option for object-oriented programmers who are less familiar with SQL." [2]
[1] Hibernate Documentation
http://www.hibernate.org/docs
[2] Comparison of iBatis, Hibernate and JPA
http://www.narendranaidu.com/2008/07/comparison-of-ibatis-hibernate-and-jpa.html
Assinar:
Postagens (Atom)