Re: Persistent Objects Using SQL

2010-05-30 Thread Darren Duncan
I understand what you're saying here. No further comments from me at this time. -- Darren Duncan Stevan Little wrote: On May 30, 2010, at 6:07 PM, Darren Duncan wrote: Stevan Little wrote: It also does not deal well with polymorphism since the ID (the object's identity) is essentially fixe

Re: Persistent Objects Using SQL

2010-05-30 Thread Stevan Little
On May 30, 2010, at 6:07 PM, Darren Duncan wrote: Stevan Little wrote: It also does not deal well with polymorphism since the ID (the object's identity) is essentially fixed to a table (usually mapped to a class). The ID (object identity) that I had in mind would be unique across all o

Re: Persistent Objects Using SQL

2010-05-30 Thread Darren Duncan
Yuval Kogman wrote: There's another implied argument, that a DB should be relational for the sake of being relational, instead of due to some other reason. If you're doing aggregation or relational queries then yes, a relational database makes sense (unless OLAP makes more sense, but whatever ;-

Re: Persistent Objects Using SQL

2010-05-30 Thread Darren Duncan
Stevan Little wrote: I think you misunderstand, KiokuDB is *not* just a JSON serialization service, it breaks up the object graph on a per-instance basis and stores each instance separately. It uses JSPON as a way to handle references from one object to another. I think perhaps you need to ta

Re: Persistent Objects Using SQL

2010-05-30 Thread Yuval Kogman
There's another implied argument, that a DB should be relational for the sake of being relational, instead of due to some other reason. If you're doing aggregation or relational queries then yes, a relational database makes sense (unless OLAP makes more sense, but whatever ;-) However, in an OLTP

Re: Persistent Objects Using SQL

2010-05-30 Thread Stevan Little
On May 30, 2010, at 2:34 AM, Darren Duncan wrote: Stevan Little wrote: On May 29, 2010, at 11:20 PM, Darren Duncan wrote: 2. Besides the ability to introspect or perform powerful searches on your objects using SQL/etc, I see another big advantage of using database storage without serializ

Moose/ Delegation/ tutorial

2010-05-30 Thread Thomas Raudaschl
I am a novice to Moose but fairly familiar with Perl. I intend to wrap a Moose package around a non-Moose class by delegation, to provide further methods by an inherited class (output into Excel and the like). The Manual is excellent, whereas it took me a while to understand how delegation is

Re: HTML::FormHandler::Moose datetime handling

2010-05-30 Thread Ovid
- Original Message > From: Ovid > Caught exception in > My::Controller::Person->edit "Can't use string ("1930-01-01T00:00:00") as a > HASH ref while "strict refs" in use at > /Library/Perl/5.10.1/HTML/FormHandler/InitResult.pm line 111." Zbigniew Lukasiak suggested I double check m

Re: Persistent Objects Using SQL

2010-05-30 Thread Oliver Charles
On Sat, May 29, 2010 at 3:37 PM, Shawn H Corey wrote: > Hi, > > Is the a standard methodology for persistent objects in Moose using SQL? Well, if you want to serialize objects as they are, you might want to consider just using KiokuDB with the DBI backend [1] -- Oliver Charles / aCiD2 1: htt

HTML::FormHandler::Moose datetime handling

2010-05-30 Thread Ovid
Not sure if this should go to this list, but also not sure where else to put this. Writing a small app and I'm using HTML::FormHandler::Moose with an SQLite database. I have a table which looks like this (not really, but close enough): CREATE TABLE person ( id INTEGER PRIMARY K