@Justin James
I want to see outsystems kill their own custom built ORM and replace it with open source
hibernate
Doing this will allow Outsystems customer to decide which database they want to use, rather than be given only two choices SQL Server or Oracle!
Hibernate/nHiberate is built for JAVA and .NET, it supports the following databases.
|
RDBMS |
Dialect |
|
MySQL5 |
org.hibernate.dialect.MySQL5Dialect |
|
MySQL5 with InnoDB |
org.hibernate.dialect.MySQL5InnoDBDialect |
|
MySQL with MyISAM |
org.hibernate.dialect.MySQLMyISAMDialect |
|
Oracle (any version) |
org.hibernate.dialect.OracleDialect |
|
Oracle 9i |
org.hibernate.dialect.Oracle9iDialect |
|
Oracle 10g |
org.hibernate.dialect.Oracle10gDialect |
|
Oracle 11g |
org.hibernate.dialect.Oracle10gDialect |
|
DB2 |
org.hibernate.dialect.DB2Dialect |
|
DB2 AS/400 |
org.hibernate.dialect.DB2400Dialect |
|
DB2 OS390 |
org.hibernate.dialect.DB2390Dialect |
|
PostgreSQL |
org.hibernate.dialect.PostgreSQLDialect |
|
Microsoft SQL Server 2000 |
org.hibernate.dialect.SQLServerDialect |
|
Microsoft SQL Server 2005 |
org.hibernate.dialect.SQLServer2005Dialect |
|
Microsoft SQL Server 2008 |
org.hibernate.dialect.SQLServer2008Dialect |
|
SAP DB |
org.hibernate.dialect.SAPDBDialect |
|
Informix |
org.hibernate.dialect.InformixDialect |
|
HypersonicSQL |
org.hibernate.dialect.HSQLDialect |
|
H2 Database |
org.hibernate.dialect.H2Dialect |
|
Ingres |
org.hibernate.dialect.IngresDialect |
|
Progress |
org.hibernate.dialect.ProgressDialect |
|
Mckoi SQL |
org.hibernate.dialect.MckoiDialect |
|
Interbase |
org.hibernate.dialect.InterbaseDialect |
|
Pointbase |
org.hibernate.dialect.PointbaseDialect |
|
FrontBase |
org.hibernate.dialect.FrontbaseDialect |
|
Firebird |
org.hibernate.dialect.FirebirdDialect |
|
Sybase |
org.hibernate.dialect.SybaseASE15Dialect |
|
Sybase Anywhere |
org.hibernate.dialect.SybaseAnywhereDialect |
Outsystems - Why should you do it?
Firstly hibernate is open source and free, it is used by many top developers and vendors such as IBM, hiberate has been tested on a large scale.
It will save you time and money, why continue to burn time and money maintaining your own custom ORM which only supports SQL Server and Orcale, then when a new version comes out you have to continue to burn time and money to support new features - how does this make sense?
If you were selling a ORM product, ok this makes sense, but your not selling an ORM product.
If you wanted a charting feature and you went your own charting tool, rather than use highcharts, I would ask you the same questions, why are you losing your time and money? how does this benefit your company in the long term? how does it benefit your customers?