Re: Perl, gdbm, and DR-DOS ...

Hm. I'm not sure what the restrictions that DR-DOS impose. I think you have three options available to you:

Abstract the database IO functions into your own module that can be different for each platform (I know that DBI is fairly abstracted already, but I'm refering to something that will make both a dbm database (for example) (ala tie) and a SQL database (ala DBI) totally transparent to the application). You can then just use whichever module is appropriate for the system (including dynamicly useing it). This will allow you to optimize the db access for each system.
Go with a straight dbm style database that will be the same everyplace.
Use a flat-file style system that you control yourself. If I need something that *must* work on a system with just basic Perl installed, this is what I do. Very inefficient and slow but I have YET to have one not work someplace*.

Regardless of which you choose, it's ALWAYS a balance between compatibility and efficiency.

Good Luck!

* I write scripts that must be runnable anywhere, at anytime, without any "setting up" required. They must all be drop-and-run. Hell, I had a requirement not long ago that it needs to be runnable from this guy's iPaq :)

Comment on Re: Perl, gdbm, and DR-DOS ...

Replies are listed 'Best First'.
Re: Re: Perl, gdbm, and DR-DOS ... by BoredByPolitics (Scribe) on Feb 03, 2001 at 16:21 UTC
Thanks for the replies, however, I've come to the conclusion that running on DR-DOS is going to be a non-starter. There are 3 large databases that will need to be maintained, so based on the feedback I've received I imagine that access will be very slow. But the real show stopper is the lack of sockets in the DR-DOS port of Perl - that leaves me with no way of communicating with the backend database on the server (unless someone knows of a way of getting sockets working in Perl under DOS). Pete	[reply]

Replies are listed 'Best First'.

Re: Re: Perl, gdbm, and DR-DOS ...
by BoredByPolitics (Scribe) on Feb 03, 2001 at 16:21 UTC

There are 3 large databases that will need to be maintained, so based on the feedback I've received I imagine that access will be very slow.

But the real show stopper is the lack of sockets in the DR-DOS port of Perl - that leaves me with no way of communicating with the backend database on the server (unless someone knows of a way of getting sockets working in Perl under DOS).

Pete

[reply]