Using ActiveRecord against SimpleDB doesn't make sense. ActiveRecord was fitted for RDBMS systems where the columns are defined. In the case of SimpleDB, the app must know what data it wants to get and how.
Need to make a layer that talk to simpleDB.
It must be able to:
1. take ruby command and return data objects.
2. cache data (see earlier post).
3. take in a definition of an document type(?)
4. accessible from both internal (within the same ruby vm) and external (rack interface?).
Can it deduce the "content" of the data from the data it get from SimpleDB. While this is neat idea, most likely we'll have problem figuring out whether 00001234 is a number 1234 or it is a String.
Something like this can be made fairly simple. Probably borrow some idea from ActiveRecords and other persistence layer implementation.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment