books and things

gav on 2002-04-28T17:56:53

Currently in my Amazon wish list are:

  1. JavaScript: The Definitive Guide
  2. Object Oriented Perl
  3. Programming Windows(r) with C# (Core Reference)
#2 is something I've been meaning to buy for a while now, #1 is a necessary evil, and #3 is because I want to start getting into C# for Win32 GUI programming.

On a perl note, I'm going to be starting to develop a wish list type thing with Openthought. It looks like a promising framework, mainly as I've completed a bigish project that used a similar technique, hidden frame using Javascript, but mine used querystring name/values instead of XML to pass parameters. But I guess using XML is cooler these days :)

I'm also thinking about starting some kind of search engine. My current one is pretty simple, fast (even with a table scan) but I want to be able to have fulltext and attribute based searching. The inverted index modules in CPAN don't seem to do exactly what I need and starting from scratch seems more fun.

Other thoughts are on on hierarchical data. Basically that's what a store is, things in sections and sub-sections with a well defined hierarchy. They don't seem to map that cleanly onto a relational model, more so on the user view than the programmer view. It's pretty hard to grok the concept of keys and joins when you are used to doing everything in excel. I'm wondering if there are any gui tools for working with hierarchical data? I have been googling without success.

Gavin


Books

vek on 2002-04-29T02:43:36

I too have found the Rhino to be invaluable and yes it's a necessary evil :-)

I bought Object Oriented Perl a month or so back and I can't recommend it enough - get it!

Store not relational?

autarch on 2002-04-29T04:16:38

In what way does a store not map well onto a relational database?

Category
----------
category_id
category_name
parent_category_id (may be NULL)

Item
------
item_id
category_id

What does it matter if this doesn't make sense for users? That's what tools and applications are for!

The data storage/retrieval mechanism should not have anything to do with what's easy for the user.