[Rails] AR db adapter for a RDF database (ATT: DHH)

[Tobias Luetke]

Hi Demetrius, 

This is a really interesting project. However I don't believe lifting
AR's close ties to SQL would not
be an favor to anyone. Indeed AR's close tie to SQL is its major
advantage over similar frameworks
which try to abstract SQL away ( and than come up with something even
worse on top like Hibernate ).

However what i recommend is to leverage rubys strength by staying
DuckType compatible with ActiveRecord. A good example of how this can
be done is the ActiveLdap project on rubyforge.
This way you can still switch between SQL and RDF on the fly and you
can probably reuse a lot of AR code like validation and similar
things.

Good luck !


On Wed, 15 Dec 2004 14:53:18 -0200, Demetrius Nunes
<demetrius at interface-ti.com.br> wrote:
> Hi people,
> 
> As I stated in a earlier message, I am using Rails on my masters degree
> and soon I will have to port my application from a relational database
> (MySql) to a RDF semantic database called Sesame.
> 
> At first, I thought that I could get away with most of the porting only
> by writing a decent database adapter, but then, examining AR closer, I
> could see that it has some strong dependencies towards relational
> mechanics and the SQL language. (The RDF database uses its own query
> language).
> 
> So, I was wondering what David and the others AR experts could say about
> this porting. Is it possible? What would be the biggest challenges? What
> parts of AR would I have to adapt besides crafting a good db adapter?
> 
> It is important to point out that I am not concerned with performance or
> any real world usage as it would serve only to demonstrate my
> application in a academic setting.
> 
> Thank you very much,
> Demetrius
> _______________________________________________
> Rails mailing list
> Rails at lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
> 


-- 
Tobi
http://blog.leetsoft.com