Re: Dbase development & tutorials

From: Ochal Christophe (co_at_nospam.orelse.fem.be)
Date: 08/13/04 

Date: Fri, 13 Aug 2004 12:57:56 +0200

SM Ryan wrote:
> # Unfortunatly, i'm unfamiliar with databases or how to create such an
> # app, does anyone know of some tutorials about this matter?
>
> On modern machines, you can often get away with using text files as
> relation tables; for example having each table row as a text file line,
> and table columns separated by tab characters. Depending on table size
> and virtual memory, you may be able to keep tables in memory. You can
> then use stdio functions and build up the functionality you need from
> there.

Hmm, that does sound feasable, but considering the restrictive nature of
PDA's and other mobile devices, space is very much important, and even
using a textfile would pose problems concerning deleting & inserting
rows and or colums... I'd have to read in the whole thing and write it
in one pass each time.

Still, this would make for a small, simple engine wich is what i'm
looking for more or less.

Relevant Pages

  • Re: session variable getting lost
    ... There are times when the virtual memory usage jumps up ... The app does not appear to be ... The message appeared in the system event log not the application event log. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Beating the dreaded rainbow pinwheel
    ... everything is slowing down even when there are few ... %CPU and Virtual Memory columns. ... If any app is using an unusually large ... amount of CPU time or virtual memory, ...
    (comp.sys.mac.system)
  • Re: Dbase development & tutorials
    ... On modern machines, you can often get away with using text files as ... and virtual memory, you may be able to keep tables in memory. ... then use stdio functions and build up the functionality you need from ... Death is the worry of the living. ...
    (comp.lang.c)
  • minimal thread stack size
    ... the goal for the customer is to avoid at most development on the app (in ... The nb of thread per process limitation is only linked to the virtual memory ... This seems to mean that our thread stack ...
    (microsoft.public.windowsce.platbuilder)