[Omaha.pm] Mapping Perl structures to a SQL table...

[Todd Christopher Hamilton]

Not done reading but you had me a "you really want to be cool"

Sterling Hanenkamp wrote:
> On Sat, Oct 31, 2009 at 8:26 AM, Dan Linder <dan at linder.org 
> <mailto:dan at linder.org>> wrote:
> 
>     2009/10/30 Sterling Hanenkamp <sterling at hanenkamp.com
>     <mailto:sterling at hanenkamp.com>>:
>      > If your data is all hashes, perhaps what you ought to look into
>     is KiokuDB,
>      > since it stores hashes very efficiently. If you can turn your
>     hashes into
>      > Moose classes while you're at it, all the better.
> 
>     The others on my team that work with this (albeit on a lesser level)
>     are even wary of non-core Perl Modules or moving to a SQL DB at all.
>     I'm taking baby-steps here hoping to help lead them into the "big
>     kids" pool via the wading pool end.
> 
>     But I will look into KiokuDB -- it looks like an interesting module.
> 
> 
> Well, if you really want to be cool, you'll convert your code to work in 
> the cloud via CouchDB or Amazon SimpleDB. RDBMS is soooo 1975. :-p All 
> the cool kids are looking to switch to some kind of cloud-stored object 
> database. (I'm not one of the cool kids, btw, since I use DBIx::Class 
> for most of my work at this point.)
> 
> KiokuDB is just interface library, like DBI. You can use memory 
> (KiokuDB::Backend::Hash), BerkeleyDB (K::B::BDB), a DBI connection 
> (K::B::DBI), Couch DB (K::B::CouchDB)or even just store one file per 
> object (K::B::File). In fact, if you wrote a Data::Dumper of 
> KiokuDB::Backend::Serialize, you could probably keep things very close 
> to what you have on the disk. :) It isn't a core module, though, and 
> depends on quite a few non-core modules, so that I can't help you with.
> 
> Stick with DBI if they want something conservative. DBI and RDBMS are 
> about as vanilla standard as it gets outside of Perl core. If you can 
> get them to go for it, DBIx::Class is a very nice way of staying away 
> from writing tons of SQL and making your code tie directly into a 
> particular DB (which is an awful place to be when you find out your 
> RDBMS limitations don't fit your app well, but now can't easily switch 
> to something else).
> 
> Cheers.
>  
> 
> 
>     Dan
> 
>     --
>     ******************* ***************** ************* ***********
>     ******* ***** *** **
>     "Quis custodiet ipsos custodes?" (Who can watch the watchmen?) -- from
>     the Satires of Juvenal
>     "I do not fear computers, I fear the lack of them." -- Isaac Asimov
>     (Author)
>     ** *** ***** ******* *********** ************* *****************
>     *******************
>     _______________________________________________
>     Omaha-pm mailing list
>     Omaha-pm at pm.org <mailto:Omaha-pm at pm.org>
>     http://mail.pm.org/mailman/listinfo/omaha-pm
> 
> 
> 
> 
> -- 
> Andrew Sterling Hanenkamp
> sterling at hanenkamp.com <mailto:sterling at hanenkamp.com>
> 785.370.4454
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Omaha-pm mailing list
> Omaha-pm at pm.org
> http://mail.pm.org/mailman/listinfo/omaha-pm