[Lazarus] Embedded database for Lazarus/Linux

Henry Vermaak henry.vermaak at gmail.com
Fri Jun 18 00:03:50 CEST 2010


On 17 June 2010 22:22, waldo kitty <wkitty42 at windstream.net> wrote:
> On 6/17/2010 15:26, Henry Vermaak wrote:
>> What happens if your structures change?
>
> since you've both the old and the new, you simply process the existing data
> file with the old structures, convert it to vars in the new structures and
> then save it to a new data file in the new format... conversion programs
> like this are pretty bog simple but they can be tedious depending on the
> number of vars you have to work with... one of the sets i work with has over
> 200 settings and options ;)

Exactly, what a joke.  If you used a database you wouldn't have to do
anything like this, just update the table definition.  No conversion
apps (what will a user make of this), no extra code in your app for
this.

>> Can you do relations?
>
> sure! you just do the same thing as in a database... you have your key here
> and it is linked in each related record over there... nothing more than a
> while loop walking thru the other data file(s) looking for a particular link
> key in each record... i was doing that before i had to become a dBase II/IV
> coder ;)

Haha, you are looping through every record of all your files?  This is
getting hilarious.

You seem to be slightly confusing app settings and app data.  Storing
app settings (like options) in a database is definitely overkill
(imho), but storing app data in an embedded database is a very good
idea.




More information about the Lazarus mailing list