[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Re: The real reason for an OASIS database?
From:       Marc Heyvaert <marc_heyvaert () yahoo ! com>
Date:       2004-05-23 14:10:50
Message-ID: 20040523141050.31997.qmail () web41505 ! mail ! yahoo ! com
[Download RAW message or body]

Hello all,

I'm just jumping in...

--- David Faure <faure@kde.org> wrote:
> 
> I think you guys are all forgetting about Kexi :)
> 
> But the problem of standardizing the file format for
> such applications is there indeed.
> Once kexi matures, I would like it very much if the
> kexi authors could look into
> defining a file format that uses as much as possible
> of the current Oasis spec
> and builds upon it to add support for databases. But
> I expect that the OO.o guys will
> do that too, if they are indeed developing such an
> application themselves, so
> maybe we'll only have to check that we can model all
> of kexi's features with it.
> 

FWIW, I have had very bad experiences with setting up
external databases. Luckily for me, my data-needs are
only very small. when I need to keep track of
something I just use a spreadsheet :)

Well if it's a bit more complicated I revert to Access
I'm afraid to admit. I tried to set up MySql. On SuSE
8.2. Should heve been very straigthforward, but it
wasn't. I had all sort of problems with permissions
and passwords. Finally I managed to do it, but I never
could get the server to work on boot. I always had to
start the thing manually.

So I think it would be great to have all these
dataprograms making use of some sort of (limited)
backend that doesn't need any sort of special install
or setup. This would probably come with a certain
price in terms of possibilities, but at the same time
the possibility to use a proper backend like MySQL
could remain open.

On reading the announcements on
http://www.koffice.org/kexi/ I don't think kexi is
going that way. Installing some sort of database will
still be necessary. Wouldn't it be possible to include
a something like SQLite with the KOffice distribution
and make ./configure check if some usable database is
already installed on the target system and otherwise
install the default. Or installe the default anyway,
unless the user has set a parameter during configure?

If all this can be done within the framework of a
common file format, that would be great.

Marc


	
		
__________________________________
Do you Yahoo!?
Yahoo! Domains – Claim yours for only $14.70/year
http://smallbusiness.promotions.yahoo.com/offer 
____________________________________
koffice mailing list
koffice@mail.kde.org
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice
[prev in list] [next in list] [prev in thread] [next in thread]