The code is really just a proof-of-concept, but is functional to the point
of being able to:
- spool in XML documents/fragments to a SQL database
- spool out SQL to the original XML, either whole documents or any subtree
There are some helper classes which might be useful elsewhere. e.g. an
REXML::StreamParser generates a stream of method calls tag_start / tag_end /
text etc; I have objects which can convert such a stream of method calls
back into the source XML, or into a tree of REXML::Element objects.
It would have been nice if REXML provided such objects itself, but I won't
raise this with the machine-gun-wielding author
Regards,
Brian.
···
On Fri, Oct 08, 2004 at 11:29:45PM +0900, George Moschovitis wrote:
ps: I would really like to have a look at your xpath->sql translator.
Rails is great, but Active Record puts relational stuff in your face pretty
much from day 1. ndb seems to offer a very nice way of working persistence
into an application without having to deal with relational tables up front,
and the possibility of not having to deal with them at all working instead
with something like Magdeline.
I am sure some of Active Record ideas of declarative definition of different
kinds of association etc. could be applicable to ndb.
Does anyone else think there may be a good marriage between the two? Action
pack would probably need a bit of clean up to remove direct dependencies on
Active Record.
much from day 1. ndb seems to offer a very nice way of working persistence
into an application without having to deal with relational tables up front,
and the possibility of not having to deal with them at all working instead
with something like Magdeline.
Does anyone else think there may be a good marriage between the two? Action
pack would probably need a bit of clean up to remove direct dependencies on
Active Record.
Hello, I am glad you like ndb.
FYI we are about to release a Web Application Engine to go along with ndb. I am sure you will find many nice ideas in the application framework as well. I hope the community will suggest many cool ideas
for that project as well. Of course we will integrate many ideas from
Rails and Active Record. The latest ndb version (to be included in the
Web Engine release) has improved api and some new features.
Navel does not accept liability for any errors, viruses or omissions in the contents of this message. The full corporate policy is available on our site.
Does anyone else think there may be a good marriage between the two? Action pack would probably need a bit of clean up to remove direct dependencies on Active Record.
I am also prepared to make any changes needed to better integrate ndb
with ActionPack.
Navel does not accept liability for any errors, viruses or omissions in the contents of this message. The full corporate policy is available on our site.
