LetoDb Elch atualizado
Enviado: 13 Abr 2023 14:54
Olá!
Não querem que eu pare de usar o DBF.
Depois de 1,5 ano mais ou menos. Elch atualizou e sincronizou com o FORK do Aleksander Czajczynski.
Ainda trabalhando no LOCATE...
E mais um aviso para os usuários do xHarbour.
Tomara que comece a usar sintaxe SQL.
Saudações,
Itamar M. Lins Jr.
Não querem que eu pare de usar o DBF.
Código: Selecionar todos
2023-04-10 02:42 UTC+0100 Rolf 'elch' Beckmann (elchs @ iesy.net)
* ChangeLog.txt
* include/srvleto.h
* source/client/letocl.c
* source/server/leto_2.c
* source/server/letoacc.c
* source/server/letofunc.c
* some left over compiler warnings about type/ signed mismatches
2023-04-09 23:01 UTC+0100 Rolf 'elch' Beckmann (elchs @ iesy.net)
* ChangeLog.txt
* include/cmdleto.h
* include/letostd.ch
* include/letocl.h
* source/client/leto1.c
* source/client/letocl.c
* source/server/leto_2.c
* source/server/letofunc.c
* tests/leto_dbf.prg
* utils/manager/console.prg
+ implementing server side LOCATE command
; note: __dbLocate() is not handled by leto_std.ch -> non optimized,
as it misses the possibility to handle literal FOR/ WHILE conditions
* moving static leto_RelOptimized() upwards in leto1.c
* adding a test for [non-]optimized LOCATE in leto_dbf.prg
2023-04-09 22:33 UTC+0100 Rolf 'elch' Beckmann (elchs @ iesy.net)
* ChangeLog.txt
* include/srvleto.h
* source/common/common.c
* adding sys/time.h and time.h for unix's, suggested by A. Czajczynski
* source/server/leto_2.c
* fix!: add crompression/ encrytion in leto_SendAnswer2() for LZ4
for the first socket - and disabling it for the second one for zLib usage
; second socket (rare, commonly none) traffic is ever plain, maybe
work for future to be ever encrypted;
; very THANKS Aleksander for pointing at the right place
* add char [P|C|X] for log-file about traffic type (debug level 15-20)
* source/server/letofunc.c
* added null termination for filenames in leto_Open|Create -table & -index
; from fork by Aleksander Czajczynski - THANKS !
* add info in letodbf.log when server demands encryption
; application can't switch back to plain traffic with LETO_TOGGLEZIP(-1)
* tests/test_file.prg
+ add a test for RTE send from server, relies on executing an UDF at server
; it depends on working second socket, nothing happens without
; test needs UDF allowed at server - not needed for real case scenario
* source/client/leto1.c
* source/client/letocl.c
* letoRddInfo() param type 'unsigned int uiConnect' => 'HB_ULONG ulConnect'
to equal Harbour prototypes
* changed casting in Leto_KeyToStr()
; from old issue report by Aleksander Czajczynski, sorry for the delay
* fix for RDDI_REFRESHCOUNT, dito from Aleksander
* fix LetoDbCreateAlias() ALIAS with trailing file extension by Aleksander
* rddleto.hbp
* rddletoaddon.hbp
+ added outcommented switch to force single threaded/ socket communication
; LETO_NO_THREAD for special use scenario, means far! less performance
* source/client/letomgmn.c
* source/server/letofunc.c
* ensure in LETO_LOCKLOCK() delay value cannot get negative
* add to kill connections rarely hindering to lock server for backup when
zero delaytime given to veto against backup [ leto_LockLock( ,,0 ) ]
; works commonly in a break of a second when there were no-win apps ;-(
+ new function LetoMgKillUser() for above, plus
* modified leto_IsAnyWaiting() for above
2023-04-06 12:02 UTC+0100 Rolf 'elch' Beckmann (elchs @ iesy.net)
* source/3rd/lz4/lib/lz4.c
* source/server/letofunc.c
* 'void' missing in func declaration without argument; clang v16 warning
- remove unused var: uiOrder in leto_Ordfunc()
* make_b32.bat
* makefile.bc
* add a warning for xHarbour users in hurry without reading the Readme.txt
and without looking into these files ... ;-)
* /bin/letodb.ini
+ add Crypt_Traffic in default ini;
recommended to be set to 1 in case of server usage over non-local network
* source/server/errint.c
* source/server/leto_2.c
* add info about active index order in case of server crash
+ new leto_errServerCrash(),
used in hb_errInternal() to only close a specific connection,
not to crash the whole server in case of serious index integrity;
need to be tested in a real scenario ...
; response to older report by Mauricio about error 9201
Ainda trabalhando no LOCATE...
E mais um aviso para os usuários do xHarbour.
Tomara que comece a usar sintaxe SQL.
Saudações,
Itamar M. Lins Jr.