Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Is there any public document describing what the highlights of the new version will be?
    • You'd have to corner David for that. I'm not sure which specifics he's released. However, I can describe things that I know are public knowledge. The object store will be one of the highlights, even though the customers won't see it. We have what is essentially a reflection based Perl object system built on top of Class::Meta, but even though we're currently targeting relational databases, there is no requirement to do so. We could target multi-value databases, XML datases, LDAP stores or even flat files, if we wanted.

      At the database layer, (which David will be describing at OSCON) the underlying system is like nothing I've seen in Perl and, to be honest, like nothing I've seen anywhere else. However, it neatly solves many issues with the object-relational impedance mismatch. This means we have to back off our initial desire to support MySQL because it's still too primitive for our needs, but I'm simultaneously building data store for PostgreSQL and SQLite to ensure that we can meet a design goal of being able to support any data store that matches the API spec. Incidentally, that was part of my frustration expressed in my recent post about lexing and parsing [perl.org].

      As a side note, I find it rather amusing that SQLite is robust enough for our needs when MySQL isn't. Unless it's changed in the last release, MySQL's updatable views only worked if you were only updating one underlying table. That's not quite useless, but close enough. You can still target MySQL with our system, but it's more work than we wanted to do right now.

      • I'll be sure to see David's talk about the database stuff. I try to keep up with the ideas being used in various O/R tools like Hibernate and ActiveRecord. Your mini-language looks a bit like what Tangram uses for querying.

        I've never really liked database views. They feel like a hack to me, i.e. just a way to avoid writing out the actual SQL for what you're doing. Security (granting limited access to specific users) is the only use for them I've seen that I liked. I'll be interested to see what you gu