On Tue, Jun 16, 2009 at 11:03 AM, Przemyslaw Czerpak<dru...@acn.waw.pl> wrote:
> What is the difference for you? None, I simply wanted to be sure I didn't miss it in the changelog. > Now in Harbour *nix builds reopened tables and indexes share file handles > and lock queues. So far I haven't added shared IO buffers and pseudo > exclusive mode with internal locking and I do not know when I will work > on it. The problem is not the Harbour performance, under Linux after the first open the others take almost no time, the overhead is in my code that was designed for "open the dbfs at start and close them to the at end of the app". I use a data dictionary structure to define users, rights, tables. fields, indexes so I expect some delay on every: DBOPEN() RUNREPORT() DBCLOSE() since every table and index is checked against the data structure. For this I'm limiting the use of threads to tasks that may take several seconds. best regards, Lorenzo _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
