You can subscribe to this list here.
2008 |
Jan
|
Feb
(5) |
Mar
(52) |
Apr
(12) |
May
(2) |
Jun
(6) |
Jul
(11) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
(20) |
May
(19) |
Jun
(21) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(7) |
Nov
(5) |
Dec
(2) |
2010 |
Jan
(8) |
Feb
(2) |
Mar
|
Apr
(6) |
May
(5) |
Jun
(26) |
Jul
(14) |
Aug
(5) |
Sep
(3) |
Oct
(3) |
Nov
(4) |
Dec
(1) |
2011 |
Jan
(1) |
Feb
(4) |
Mar
(1) |
Apr
(13) |
May
(10) |
Jun
(10) |
Jul
(7) |
Aug
(5) |
Sep
(2) |
Oct
(6) |
Nov
(1) |
Dec
|
2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(1) |
May
(2) |
Jun
(4) |
Jul
(2) |
Aug
(8) |
Sep
(6) |
Oct
(1) |
Nov
(5) |
Dec
(6) |
2013 |
Jan
(5) |
Feb
|
Mar
(12) |
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(6) |
Dec
(27) |
2014 |
Jan
(13) |
Feb
(6) |
Mar
(8) |
Apr
(2) |
May
|
Jun
(6) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
2015 |
Jan
(6) |
Feb
(7) |
Mar
(7) |
Apr
(16) |
May
(2) |
Jun
(10) |
Jul
(21) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
(15) |
Nov
(2) |
Dec
(4) |
From: gabor <ga...@po...> - 2016-12-15 18:25:37
|
Hello. Previous code only accept spaces (which are omitted), digits and dot sign (decimal separator). And if it encounters any other character, including minus, it returns an error (2) and field is not updated. Regards, Michał. W dniu 2016-12-12 o 12:20, Alexander S.Kresin pisze: > Sorry for a late answer and thanks for a patch. > But I don't see problems with 'negative values for the field type "N"' > in current code. Your patch provides additional checks for a number > validity, but doesn't change the way how a number is stored. > > Regards, Alexander. > > gabor пишет: >> Hello. >> Function LetoDbPutField does not set all kinds of fields and does not >> allow entering negative values for the field type "N". >> Patch attached. >> > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/xeonphi > _______________________________________________ > Letodb-developers mailing list > Let...@li... > https://lists.sourceforge.net/lists/listinfo/letodb-developers > |
From: Alexander S.K. <al...@be...> - 2016-12-12 11:46:11
|
2016-12-12 14:44 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/client/letocl.c * source/server/letofunc.c ! Few fixes, provided by Michal. |
From: Alexander S.K. <al...@be...> - 2016-12-12 11:36:48
|
Sorry for a late answer and thanks for a patch. But I don't see problems with 'negative values for the field type "N"' in current code. Your patch provides additional checks for a number validity, but doesn't change the way how a number is stored. Regards, Alexander. gabor пишет: > Hello. > Function LetoDbPutField does not set all kinds of fields and does not > allow entering negative values for the field type "N". > Patch attached. > |
From: Nenad B. <nba...@wi...> - 2016-12-11 02:05:19
|
Hello! Please pay attention to the bug which is reported by Rolf in harbour-users. I occasionally get an error "lock required" and this is the most likely cause: "I reported earlier about origin LetoDB 2.17-b3 misbehaviour. A correction, in mode: Share_Tables = 0, nobody may notice the "misfeature". But with Share_Tables = 1, you can watch this: first user set Rlock() at record 2, writes something into a field second user set a Flock() when at record 1, and immediate dbunlock(), then first user for sure is astonished that his Rlock() is gone, no changes are written with his DbUnlock(), instead in server logs can be find: Lock required! and warning message shell pop up. If this pair: Flock()/ DbUnlock() happens in between another users pair: DbAppend()/ DBUNLOCK(), you will get: Error Leto/1021 Data type error with next DbAppend(), DbSkip(), .. -- and an empty ? record(). Cause of this: a 'special' designed file-unlock is needed, plus Flock() generally have to respect Rlock()." regards, NB |
From: gabor <ga...@po...> - 2016-11-07 11:38:08
|
Hello. Integer fields with size 1 and 3 (8bit and 24bit) are not updated by letodb. Patch attached. Best regards, Michał. |
From: gabor <ga...@po...> - 2016-11-06 22:56:08
|
Hello. Function LetoDbPutField does not set all kinds of fields and does not allow entering negative values for the field type "N". Patch attached. Regards, Michał. |
From: Alexander S.K. <al...@be...> - 2016-10-27 10:53:15
|
Itamar M. Lins Jr. Lins пишет: > ... > ERROR! ParseCommand() > goto 8 1;pdv01;A; > ERROR! ParseCommand() > seek 8 pdv01;Q;♥078 > ... Could you provide a short code sample, which causes these errors ? Regards, Alexander. |
From: Itamar M. L. J. L. <ita...@gm...> - 2016-10-25 13:50:42
|
Hi! Changelog 2016-10-21 11:04 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/server/letofunc.c ! Bug fixed in a handler of FLock() function in No_Save_WA mode. C:\Users\Itamar\Documents\GitHub\letodb-code [master = +3 ~0 -0 !]> hbmk2 .\rddl eto.hbp -rebuildall hbmk2: Harbour: Compilando módulos... hbmk2: Compilando... ../../../../source/client/letocl.c: In function 'leto_AddFields': ../../../../source/client/letocl.c:1761:7: warning: this 'while' clause does not guard... [-Wmisleading-indentation] while( *ptr != ';' ) ptr++; ptr++; ^~~~~ ../../../../source/client/letocl.c:1761:35: note: ...this statement, but the lat ter is misleadingly indented as if it is guarded by the 'while' while( *ptr != ';' ) ptr++; ptr++; ^~~ ../../../../source/client/letocl.c:1765:7: warning: this 'while' clause does not guard... [-Wmisleading-indentation] while( *ptr != ';' ) ptr++; ptr++; ^~~~~ ../../../../source/client/letocl.c:1765:35: note: ...this statement, but the lat ter is misleadingly indented as if it is guarded by the 'while' while( *ptr != ';' ) ptr++; ptr++; ^~~ ../../../../source/client/letocl.c:1767:7: warning: this 'while' clause does not guard... [-Wmisleading-indentation] while( *ptr != ';' ) ptr++; ptr++; ^~~~~ ../../../../source/client/letocl.c:1767:35: note: ...this statement, but the lat ter is misleadingly indented as if it is guarded by the 'while' while( *ptr != ';' ) ptr++; ptr++; ^~~ ../../../../source/client/letocl.c: In function 'LetoDbCreateTable': ../../../../source/client/letocl.c:1834:8: warning: potential null pointer deref erence [-Wnull-dereference] if( *ptr == '1' ) ^~~~ ../../../../source/client/letocl.c: In function 'LetoDbOpenTable': ../../../../source/client/letocl.c:1902:8: warning: potential null pointer deref erence [-Wnull-dereference] if( *ptr == '1' ) ^~~~ In file included from ../../../../source/client/letocl.c:66:0: ../../../../source/client/letocl.c: In function 'LetoDbSkip': C:/HB34/include/hbdefs.h:1394:80: warning: null pointer dereference [-Wnull-dere ference] ( ( ( HB_U32 ) (( const HB_BYTE * )( p )) [ 0 ] ) | \ ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~ ../../../../source/client/letocl.c:845:19: note: in expansion of macro 'HB_GET_L E_UINT24' ulDataLen = HB_GET_LE_UINT24( ptr ) + 3; ^ C:/HB34/include/hbdefs.h:1395:80: warning: null pointer dereference [-Wnull-dere ference] ( ( HB_U32 ) (( const HB_BYTE * )( p )) [ 1 ] << 8 ) | \ ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~ ../../../../source/client/letocl.c:845:19: note: in expansion of macro 'HB_GET_L E_UINT24' ulDataLen = HB_GET_LE_UINT24( ptr ) + 3; ^ C:/HB34/include/hbdefs.h:1396:80: warning: null pointer dereference [-Wnull-dere ference] ( ( HB_U32 ) (( const HB_BYTE * )( p )) [ 2 ] << 16 ) ) ) ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~ ../../../../source/client/letocl.c:845:19: note: in expansion of macro 'HB_GET_L E_UINT24' ulDataLen = HB_GET_LE_UINT24( ptr ) + 3; ^ ../../../../source/client/leto1.c: In function 'letoOrderInfo': ../../../../source/client/leto1.c:3390:14: warning: 'pConnection' may be used un initialized in this function [-Wmaybe-uninitialized] if( LetoCheckServerVer( pConnection, 100 ) ) ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../../../source/client/letomgmn.c: In function 'HB_FUN_LETO_MGGETUSERS': ../../../../source/client/letomgmn.c:552:13: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:552:59: note: ...this statement, but the la tter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c:561:19: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:561:65: note: ...this statement, but the la tter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c: In function 'HB_FUN_LETO_MGGETTABLES': ../../../../source/client/letomgmn.c:596:13: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:596:59: note: ...this statement, but the la tter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c:605:19: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:605:65: note: ...this statement, but the la tter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c: In function 'HB_FUN_LETO_MGGETLOCKS': ../../../../source/client/letomgmn.c:640:13: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:640:59: note: ...this statement, but the la tter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c:649:19: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:649:65: note: ...this statement, but the la tter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c: In function 'HB_FUN_LETO_VARGETLIST': ../../../../source/client/letomgmn.c:1139:16: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:1139:62: note: ...this statement, but the l atter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c:1142:16: warning: this 'if' clause does not guard... [-Wmisleading-indentation] if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~ ../../../../source/client/letomgmn.c:1142:62: note: ...this statement, but the l atter is misleadingly indented as if it is guarded by the 'if' if( !LetoGetCmdItem( &ptr, szData ) ) return; ptr ++; ^~~ ../../../../source/client/letomgmn.c: In function 'HB_FUN_LETO_VARSET': ../../../../source/client/letomgmn.c:976:17: warning: 'pRetValue' may be used un initialized in this function [-Wmaybe-uninitialized] ptr = *pRetValue; ~~~~^~~~~~~~~~~~ In file included from ../../../../source/common/hbip.c:100:0: C:/mingw32/i686-w64-mingw32/include/winsock2.h:15:2: warning: #warning Please in clude winsock2.h before windows.h [-Wcpp] #warning Please include winsock2.h before windows.h ^~~~~~~ hbmk2: Criando biblioteca estática... lib\librddleto.a C:\Users\Itamar\Documents\GitHub\letodb-code [master = +3 ~0 -0 !]> Best regards, Itamar M. Lins Jr. |
From: Itamar M. L. J. L. <ita...@gm...> - 2016-10-24 12:02:59
|
---------- Forwarded message ---------- From: Itamar M. Lins Jr. Lins <ita...@gm...> Date: 2016-10-24 9:01 GMT-03:00 Subject: Re: [Letodb-developers] Many errors with letodb v.2.17b3. To: "Alexander S.Kresin" <al...@be...> Hi! Test with 2016-10-21 11:04 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/server/letofunc.c ! Bug fixed in a handler of FLock() function in No_Save_WA mode. Git, no ID info :( My leto client lib: 21/10/16 14:54 126.347 letocl.dll 21/10/16 14:47 101.154 libleto.a 21/10/16 14:41 205.476 librddleto.a File, letodb.log 10/24/16 08:11:31: Leto DB Server has been started. Leto DB Server v.2.17b3 ! INIT: DataPath=c:\master\dados, ShareTables=1, MaxUser s=500, MaxTables=5000, CacheRecords=20 ERROR! ParseCommand() goto 8 1;pdv01;A; ERROR! ParseCommand() seek 8 pdv01;Q;♥078 ERROR! ParseCommand() 12968 ; ERROR! ParseCommand() goto 4 1;eq03;A; ERROR! ParseCommand() skip 4 1;4579;eq03;A; ERROR! ParseCommand() 17060 Q; ERROR! ParseCommand() 17060 Q; And file, letodb_0.log ERROR!!!!!!!!!!! hb_rddRequestArea! 8 ERROR!!!!!!!!!!! hb_rddRequestArea! 8 ERROR!!!!!!!!!!! hb_rddRequestArea! 8 ERROR!!!!!!!!!!! hb_rddRequestArea! 8 ERROR!!!!!!!!!!! hb_rddRequestArea! 8 ERROR!!!!!!!!!!! hb_rddRequestArea! 8 Works fine with letodb SVN. /* $Id: Changelog,v 1.350.2.242 2015/08/01 20:23:30 ptsarenko Exp $ */ Best regards, Itamar M. Lins Jr. 2016-10-21 4:28 GMT-03:00 Alexander S.Kresin <al...@be...>: > Itamar M. Lins Jr. Lins пишет: > > Hi! > > I update for Leto DB Server v.2.17b3 GIT Version, I get many errors. > > My Letodb.log > > ERROR! ParseCommand() > > seek 19 eq02;Q; > > HT000106 > > ... > > > > Works fine with final version of soucerforge, 2015 > > > > What is the "final version of soucerforge, 2015", what is the version > number ? > Check your rddleto.lib, which is linked to your client applications. > It seems that it is very old ( < 2013 ). > > Regards, Alexander. > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Letodb-developers mailing list > Let...@li... > https://lists.sourceforge.net/lists/listinfo/letodb-developers > |
From: Alexander S.K. <al...@be...> - 2016-10-21 08:06:24
|
2016-10-21 11:04 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/server/letofunc.c ! Bug fixed in a handler of FLock() function in No_Save_WA mode. Regards, Alexander. |
From: Alexander S.K. <al...@be...> - 2016-10-21 07:28:33
|
Itamar M. Lins Jr. Lins пишет: > Hi! > I update for Leto DB Server v.2.17b3 GIT Version, I get many errors. > My Letodb.log > ERROR! ParseCommand() > seek 19 eq02;Q; > HT000106 > ... > > Works fine with final version of soucerforge, 2015 > What is the "final version of soucerforge, 2015", what is the version number ? Check your rddleto.lib, which is linked to your client applications. It seems that it is very old ( < 2013 ). Regards, Alexander. |
From: Itamar M. L. J. L. <ita...@gm...> - 2016-10-20 15:35:33
|
Hi! I update for Leto DB Server v.2.17b3 GIT Version, I get many errors. My Letodb.log ERROR! ParseCommand() seek 19 eq02;Q; HT000106 ERROR! ParseCommand() goto 19 -1;eq03;A; ERROR! ParseCommand() seek 19 eq02;Q; EL50423 ERROR! ParseCommand() seek 19 eq02;Q; TI2205 ERROR! ParseCommand() seek 19 eq02;Q; HA0269 ERROR! ParseCommand() seek 19 eq02;Q; Works fine with final version of soucerforge, 2015 My letodb.ini is: Port = 2812 Logfile = "letodb.log" DEFAULT_DRIVER = CDX DATAPATH = c:\MASTER\DADOS ENABLEFILEFUNC = 1 CRYPT_TRAFFIC = 0 PASS_FOR_LOGIN = 0 PASS_FOR_MANAGE = 0 PASS_FOR_DATA = 0 Share_Tables = 0 [DATABASE] DataPath = c:\MASTER\DADOS Driver = CDX Best regards, Itamar M. Lins Jr. |
From: Alexander S.K. <al...@be...> - 2016-10-19 06:35:11
|
Itamar M. Lins Jr. Lins пишет: > Hi! > Readme.ini I found this: > Cache_Records - The number of records to read into the cache > > Which is the default value ? 10 records. More info about caching you may find in a new Leto FAQ: http://www.kresin.ru/en/letofaq.html#_m5 Regards, Alexander. |
From: Itamar M. L. J. L. <ita...@gm...> - 2016-10-18 12:47:36
|
Hi! Readme.ini I found this: Cache_Records - The number of records to read into the cache Which is the default value ? Best regards, Itamar M. Lins Jr. |
From: Alexander S.K. <al...@be...> - 2016-10-12 07:22:12
|
2016-10-12 10:12 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * include/funcleto.h * build number is set to 3. Source package letodb-2.17-b3.src.zip has been uploaded to Sourceforge. Regards, Alexander. |
From: Alex <al...@be...> - 2016-10-11 17:07:08
|
2016-10-11 20:05 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/client/letomgmn.c * leto_setCurrentConnection() may receive now a server path string or a connection number. It returns the previous connection number. If no one paarameter is passed, it works as leto_getCurrentConnection(). * leto_ping() may receive now a server path string or a connection number. * Readme.txt * readme_rus.txt * Information changed about leto_setCurrentConnection(), a line about leto_Ping() added. Regards, Alexander. ________________________________________________ |
From: Alexander S.K. <al...@be...> - 2016-10-10 11:45:14
|
2016-10-10 14:24 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * include/letocl.h * source/client/letocl.c * LetoPing() function added. * Setting of connection error s_iError = 1000 moved from leto_SendRecv() to leto_DataSendRecv() to make it possible to use leto_FError() from file functions. * source/client/letomgmn.c * Leto_Ping() functionn added - it checks the current connection state: returns .T. if it is Ok. Refards, Alexander. |
From: Nenad B. <nba...@wi...> - 2016-10-07 11:25:13
|
Thank you very much! This is very important and I think that will be very useful. Regards, NB -----Original Message----- From: Alexander S.Kresin [mailto:al...@be...] Sent: Friday, October 07, 2016 11:59 AM To: let...@li... Subject: [Letodb-developers] LetoDB FAQ Hi, I've created a new page on my site, LetoDB FAQ: http://www.kresin.ru/en/letofaq.html This is an effort to gather in one place comments about important aspects of LetoDb usage for to not look for them in forums and mail arhives. It's quite small yet, I will supplement it from time to time. Suggestions about adding new items are appreciated, you may post them in LetoDB FAQ page in comments section. Regards, Alexander. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Letodb-developers mailing list Let...@li... https://lists.sourceforge.net/lists/listinfo/letodb-developers |
From: Alexander S.K. <al...@be...> - 2016-10-07 09:58:34
|
Hi, I've created a new page on my site, LetoDB FAQ: http://www.kresin.ru/en/letofaq.html This is an effort to gather in one place comments about important aspects of LetoDb usage for to not look for them in forums and mail arhives. It's quite small yet, I will supplement it from time to time. Suggestions about adding new items are appreciated, you may post them in LetoDB FAQ page in comments section. Regards, Alexander. |
From: Alex <al...@be...> - 2016-10-01 05:46:29
|
> Is this working for DBFNTX too? > Yes. Regards, Alexander. ________________________________________________ |
From: Nenad B. <nba...@wi...> - 2016-10-01 00:21:11
|
Is this working for DBFNTX too? Regards, NB -----Original Message----- From: Alexander S.Kresin [mailto:al...@be...] Sent: Friday, September 30, 2016 8:14 AM To: let...@li... Subject: [Letodb-developers] Changelog 2016-09-30 08:50 UTC+0300 Alexander Kresin 2016-09-30 08:50 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/server/letofunc.c ! Yet another fixes for No_Save_WA mode. Works normally now for a simple tests. * source/server/server.prg * Requests for few bit functions added. By default, LetoDb server opens all files in exclusive mode and these opened files are shared by all users. This allows to decrease the number of opened files, to save memory and to speed up some operations - because exclusive mode works faster than shared (no need for locks, more buffers). But, on the other side, this mode doesn't allow to use internal DBFCDX index buffers, because each new operation for a request from another user resets them - this may cause slowdown in some cases and more intensive disk usage. If you set in letodb.ini No_Save_WA = 1, you switch LetoDb server to another mode: opened files are not shared between users, each workarea is "personal" as in usual DBFCDX based application. Now, after latest fixes, this mode should work - it works here, with a simple tests, but isn't tested properly yet. And I know nothing yet, will it be faster or no. Anyway, the benefit may appear for a relatively big files. Testing of this mode is appreciated. Regards, Alexander. ------------------------------------------------------------------------------ _______________________________________________ Letodb-developers mailing list Let...@li... https://lists.sourceforge.net/lists/listinfo/letodb-developers |
From: Alexander S.K. <al...@be...> - 2016-09-30 06:13:25
|
2016-09-30 08:50 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/server/letofunc.c ! Yet another fixes for No_Save_WA mode. Works normally now for a simple tests. * source/server/server.prg * Requests for few bit functions added. By default, LetoDb server opens all files in exclusive mode and these opened files are shared by all users. This allows to decrease the number of opened files, to save memory and to speed up some operations - because exclusive mode works faster than shared (no need for locks, more buffers). But, on the other side, this mode doesn't allow to use internal DBFCDX index buffers, because each new operation for a request from another user resets them - this may cause slowdown in some cases and more intensive disk usage. If you set in letodb.ini No_Save_WA = 1, you switch LetoDb server to another mode: opened files are not shared between users, each workarea is "personal" as in usual DBFCDX based application. Now, after latest fixes, this mode should work - it works here, with a simple tests, but isn't tested properly yet. And I know nothing yet, will it be faster or no. Anyway, the benefit may appear for a relatively big files. Testing of this mode is appreciated. Regards, Alexander. |
From: Alexander S.K. <al...@be...> - 2016-09-28 10:18:05
|
2016-09-28 13:08 UTC+0300 Alexander Kresin (alex/at/belacy.ru) * source/server/letofunc.c ! Few fixes for No_Save_WA mode (this mode doesn't work normally yet). ! Few warnings fixed. Regards, Alexander. |
From: Alexander S.K. <al...@be...> - 2016-09-27 13:35:44
|
Itamar M. Lins Jr. Lins пишет: > Hi! > leto_file() not work 2016-09-20 13:26 UTC+0300 Alexander Kresin. > A other problem is: > -----8<---- > Leto DB Server v.2.16b1 ! INIT: DataPath=c:\CLIENTES\BLOCOLAR, > ShareTables=0, Ma > xUsers=500, MaxTables=5000, CacheRecords=100 > 09/21/16 08:59:55: Server has been closed. > > 09/24/16 08:33:07: Leto DB Server has been started. > > Leto DB Server v.2.17b2 ! INIT: DataPath=, ShareTables=0, MaxUsers=500, > MaxTable > s=5000, CacheRecords=10 > --->8--- > > v.2.17b2 not show correct DATAPATH, into letodb.log I just checked it - all works normally. The DataPath is shown, and the leto_File() works (tested with tests\test_file.prg). Is the datapath set in your letodb.ini, is the EnableFileFunc set to 1 ? Regards, Alexander. |
From: Itamar M. L. J. L. <ita...@gm...> - 2016-09-24 11:41:35
|
Hi! leto_file() not work 2016-09-20 13:26 UTC+0300 Alexander Kresin. A other problem is: -----8<---- Leto DB Server v.2.16b1 ! INIT: DataPath=c:\CLIENTES\BLOCOLAR, ShareTables=0, Ma xUsers=500, MaxTables=5000, CacheRecords=100 09/21/16 08:59:55: Server has been closed. 09/24/16 08:33:07: Leto DB Server has been started. Leto DB Server v.2.17b2 ! INIT: DataPath=, ShareTables=0, MaxUsers=500, MaxTable s=5000, CacheRecords=10 --->8--- v.2.17b2 not show correct DATAPATH, into letodb.log Best regads, Itamar M. Lins Jr. |