Re: Small Database Software Recommendation
the file system and associated tools is exactly what you need man join man sort man cut man awk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Small Database Software Recommendation
Hi Guys, I'm looking for a small database application to create a database of all may dvds and cds. I think mysql my be too much overkill, since it would be running on my laptop. Any suggestions. TIA Rod ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Small Database Software Recommendation
On Sat, 21 Jun 2003, Rod Person wrote: Hi Guys, I'm looking for a small database application to create a database of all may dvds and cds. I think mysql my be too much overkill, since it would be running on my laptop. Any suggestions. If that's all you're using it for you don't need anything more than a simple formatted text file that can be queried by any perl, awk or shell script. Cheers, Viktor ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Small Database Software Recommendation
Rod Person wrote to [EMAIL PROTECTED]:
Hi Guys,
I'm looking for a small database application to create a database of all
may dvds and cds. I think mysql my be too much overkill, since it would
be running on my laptop. Any suggestions.
Yes.
It's raining in Saskatoon. Feels like a rant coming on. :-)
Fully define the requirements before choosing the technology.
MySQL *might* be overkill. I could recommend anything from flat files to
Oracle, though, and be wrong, depending on exactly what it is you want
to accomplish. For a simple key/value hash that you might encounter in
the decades old album catalogue problem, Berkeley DB, or maybe Perl's
built-in %hash functions would be the way to go.
Consider your requirements. What is the system for? Who will be using
it? What hidden and evident features must it have? What *tasks* (a.k.a.
use cases) will the users carry out? What other less tangible goals
are to be accomplished by the system? Which constraints and standards
must the system adhere to?
Once you have the above, you can begin to consider the architecture of
your system, and, once you've done that, choosing a specific technology
might be appropriate.
Requirements specification is *never* overkill.
As far as defining less tangible goals, though, I want to learn ${X}
is a valid goal.
Hope this helps,
- Ryan
--
Ryan Thompson [EMAIL PROTECTED]
SaskNow Technologies - http://www.sasknow.com
901-1st Avenue North - Saskatoon, SK - S7K 1Y4
Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon
Toll-Free: 877-727-5669 (877-SASKNOW) North America
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Small Database Software Recommendation
On Saturday 21 June 2003 08:45 pm, Ryan Thompson wrote:
As far as defining less tangible goals, though, I want to learn
${X} is a valid goal.
And there is nothing quite as motivating as a task *you* want to do.
Especially compared against class assignment or something the boss
thinks should be done.
--
David Kelly N4HHE, [EMAIL PROTECTED]
=
The human mind ordinarily operates at only ten percent of its
capacity -- the rest is overhead for the operating system.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
