As I understand it, the biggest issue with getting automatic JDBC database support in ActiveRecord is trying to figure out type mappings, yes? On this aspect I would offer a few thoughts:
- There ought to be a way to do a "best guess" mapping across the board based on Driver metadata. I understand that JDBC types often map to multiple database types, but there ought to be additional metadata or a heuristic we could use to improve our guesses.
- As the adapter gets more widespread use, we'll certainly gather information on more databases; we could in the future provide more specific mappings for specific databases, or provide a configuration mechanism to allow users to customize the process.
- Other ORM layers do this mapping between Java and database types...how do they do it? I would imagine the Hibernates and iBatises of the world have their own complexiful type-mapping logic.
- Ultimately the selling point of ActiveRecord/JDBC is lost without some sort of automatic support, even if it's not rock-solid. We need something.
Other than type mapping, what needs to be done with the adapter? What of ActiveRecord doesn't it do or do well (for our simple case of MySQL with hard-coded mappings)?
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ www.jruby.org
Application Architect @ www.ventera.com
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
