Re: More than one way to skin an architecture

That sounds like a really cool project.

Just one thought: If you're wanting to have persistence, and you don't mind using DBI, why not just use a database (even a small one like SQLite)?

...roboticus

Comment on Re: More than one way to skin an architecture

Replies are listed 'Best First'.
Re^2: More than one way to skin an architecture by mcoblentz (Scribe) on Mar 17, 2008 at 23:55 UTC
Hi roboticus, Fair question. My initial, instinctive response was because 1) I don't have anything installed on the laptop and didn't really want learn another program (I'm okay at SQL but not great by any means). And setting up primary and foreign keys, etc., really is out of my league at the moment. 2) I was thinking that I would move all of this to my website eventually and run it there, so text processing and perl would be better; but hey, I have MySQL on the site already, so... ... it's not a bad idea and I really should think about it. Queries would be just as simple; porting to a web host would be fairly easy; and dropping old data wouldn't be that hard. Food for thought.	[reply]

Replies are listed 'Best First'.

Re^2: More than one way to skin an architecture
by mcoblentz (Scribe) on Mar 17, 2008 at 23:55 UTC

Fair question. My initial, instinctive response was because 1) I don't have anything installed on the laptop and didn't really want learn another program (I'm okay at SQL but not great by any means). And setting up primary and foreign keys, etc., really is out of my league at the moment. 2) I was thinking that I would move all of this to my website eventually and run it there, so text processing and perl would be better; but hey, I have MySQL on the site already, so...

... it's not a bad idea and I really should think about it. Queries would be just as simple; porting to a web host would be fairly easy; and dropping old data wouldn't be that hard.

Food for thought.

[reply]