On Tue, 2002-05-28 at 02:57, Richie de Almeida wrote: > I haven't tried it, but I saw a CD database app on offer at apps.kde.com, > sorry I don't recall the name but you can search their database, I recall it > runs on MySQL or postgresql---
Sorry :( No QT or KDE here.
> If you want to roll-your-own CD DB app have a look at "Adabas" it comes as an
> add-on package to StarOffice 6.0 and is meant to be a desktop-database a-la
> MS Access. BTW StartOffice 6.0 is gratis if you sign on to Mandrake Club
> Silver membership.
This raises two problems. I'm looking for a real solution. I see
there are around quite a lot of PHP scripts done over night that require
both Apache and a SQL server up. I'm trying to find a real solution. I
can't say anything against this approach either, as in case I'll do my
own app, probably I'll go the scripting way for sure, but just with the
SQL database up. This is why another type of database would come in
handy. Something that is like a lib and can be included, something that
doesn't "talk" with a server but rather acts directly on the file(s)
containing the database.
About an Access like database - the answer is even stronger. I'd
rather go the PHP way and use the functionality of MySQL for example for
other uses as well rather than that.
About memberships... I usually don't register with anything. Or maybe
this is just an excuse and in reality there's something else... I don't
know ;-)
On Mon, 2002-05-27 at 19:57, James wrote:
> You might try Gaby. It's a lighter weight Dbase like the old DBaseIV
of
> days gone by. And one of the samples it comes with is a Dbase and gui
> for editing/cataloging your CD's It also has a Gui for creating these
> Data Bases much like DBaseIV. You can grab it here.
> http://membres.lycos.fr/fpeters/gaby/
I will check that. Thanks a lot.
On Tue, 2002-05-28 at 11:24, Simon Naish wrote:
> Try GTKtalog (think thats the right spelling ) it's probably the one
that Richie has seen. You just slap the cd in and let it do its thing.
It will look through zips and RPMs to get a omplete list of files, so
unless you have a long long time to wait dont put those distro disks in.
I made this mistake ;-| doh! It took about 45 minutes to read the disk,
but it seemed like a fine effort to reproduce the contents. That was a
while ago, I assume its got even better since.
Yes, that is the right spelling. And I used it in the beginning. It
would be the perfect project if your database doesn't go over 20-30
CDs. I have 256M of RAM and it crashed before reaching 60 CDs... this
is because of a design problem. It loads everything up in the memory.
That makes it awful slow to load, and it just eats up your RAM as you
add more files. And, amazingly, even with the whole database in the
memory it is still slow.
signature.asc
Description: This is a digitally signed message part
