On Jul 3, 2009, at 9:10 AM, Sam Rowe wrote:
>
> If attention is being paid to this section of the code, would any
> consideration be made to moving away from RoR/RDBMS toward something
> more suited to the task? Or even just augmenting the available
> back-ends?
>
> It seems like using an RDBMS for this data not only doesn't benefit
> from RDBMS features, but also makes it harder to store and retrieve
> it. Would something like Tokyo Cabinet be a better fit?
>
> Of course you might say "It's not hard for me, RoR does it for me!"
> but we've had other uses for our storedconfigs database that weren't
> exactly RoR-friendly.
I'm certainly amenable to the idea.
We looked into CouchDB but it exploded pretty quickly with either one
large record or one record per resource.
And changing the backend for writing is pretty easy, but we need to
build an abstract interface for querying, and that's not so easy.
We're currently building Rails queries directly in the parser, and
that'd need to switch to a more abstract form.
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
-- (attributed to) Brian W. Kernighan (unconfirmed)
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
