Leaderboard

First, SQLite is a simple library, not a client-server design. SQLite can only proceed with ONE SQL transaction at any given time. Also SQLite locks the entire DB file, not a specific table or row. When SQLite detects a BUSY situation when transaction A enters execution (another SQL transaction B in being processed, plus possible other transactions C, D, ... in BUSY state as well) and a non-zero timeout is in place for A, it continues processing B and repeatedly checks if A, C, D, ... are still in BUSY state until their respective timeout value exipres or B terminates and clears the way for others. SQLite doesn't queue BUSY transactions waiting for clearance in a FIFO or like. It randomly selects one of the waiting transaction and gives it a chance to process. That means that with the previous enumeration, when B terminates, SQLite is free to randomly select D to run, then F, then C, then E, until it selects A. That's why I mean "the longest possible sequence of transactions issued by all users of the library", because you may be unlucky and have your thing clear to run way after what you'd expect. That's also why it should be forbiden to group in a single transaction something like: select for change a number of rows, wait for user to chose the ones they need change, take the lunch break, update some data and finish the transaction. Some client-server designs can cope with this but at the expense of serious internal complexity to deal with parallel updates. About autoincrement: you ever need this except if your application can't cope with duplicate use of rowid over time. Example without autoincrement: create table T (id integer primary key, name text); insert into T (name) values ('Alice'), ('Bob'), ('Charlie'), ('Dom'), ('Elon'); delete from T where name glob '*o*'; insert into T (name) values ('Eve'); You obtain: id name 1 Alice 3 Charlie 4 Eve Instead, with this: create table T (id integer primary key autoincrement, name text); insert into T (name) values ('Alice'), ('Bob'), ('Charlie'), ('Dom'), ('Elon'); delete from T where name glob '*o*'; insert into T (name) values ('Eve'); You get: id name 1 Alice 3 Charlie 6 Eve With autoincrement, once a given rowid has been used, you're sure it won't be reused ever. This a very rare use case and forces SQLite to maintain sqlite_sequence for this table.

A lot of changes are missing from that version of the history, you need to check autoit_changelog_complete.txt. Earliest reference to Maps i can find is 3.3.13.6 (18th, 2014) (Beta), where it changed from being called Tables to Maps, but i cannot find any references to Tables earlier at a glance.

@CYCho, testing on Windows 7, the resize does not function correctly - the title bar does not resize while the edge is dragged, only when the drag ends.

Hi everyone 👋 , thank you in advance for looking at the little project and for thinking about supporting it (me) 😀 . Introduction I have a small AutoIt + SQLite GitHub project (sqlite-showcase). This serves at 1️⃣. glance to demonstrate how to use SQLite using concrete examples. If questions arise in the English or German forum about SQLite, I can provide direct assistance using the project and its example data. As 2️⃣. perspective, this project is intended as a module for a subsequent project that deals with something more than "just" AutoIt + SQLite - but more on that another time. I deliberately refrain from writing and explaining too many details here, because it is important to me, among other things, that the explanation on GitHub, in the form of a README file, can be handled or whether I need to make improvements there. Testing So far I have been able to test the project under Windows 10 (x64), with AutoIt v3.3.16.1 and with SQLite v3.49.0. Due to the support of the german AutoIt forum member(s), I could also test with Windows 11. Now I would be very happy if someone among you (several people are welcome) 🤗 would test other system configurations. See the following table: The test consists of the following parts: Read the README, understand what to do ==> If there are already problems understanding this, then I have to make improvements. Setting up the project (getting started) ==> Is the explanation in the README sufficient? You can test it on Windows 10 x86? Then please, great. Do you have an old version of AutoIt that you can test with? That's exactly what I need ==> Thanks. You want to try a different SQLite version? Why not, I appreciate it. Are the few SQLite functions running correctly or are there any errors? They shouldn't, but if they do, please let me know. Preconditions You don't need Git or GitHub, although Git is an advantage. A simple download of the project (zip) is completely sufficient (see README). Just a little time, curiosity, interest in learning something new or putting my approach to the test 😅 . 🔥 CHANGELOG can be found here. --------------------------------- Thank you very much for your interest and for your support. If you have any questions, please let me know. Thanks. Best regards Sven Update: Testing complete.

I have found out that i MAY want to change the go to declaration behavior for this extension, and need to hear what users of the application thinks. Currently, when choosing go to declaration, for a variable, it will simply go to the top declaration that matches the identifier, taking into account the precedence of scoped variables. But i am realizing that i can give more than one result in my declaration provider, and other languages like JavaScript does this. So: would it be preferred that the behavior is like now or that if more than one exists, a collection of declarations will be shown to navigate between? Thanks in advance, for you feedback! here is a screenshot of the example in JavaScript:

I simulated a title bar for my zPlayer in order to utilize the empty space in the title bar. That was necessary because I wanted to keep the size of the GUI to the minimum. In the case of zPlayer, the GUI was not resizable, so It did not not need the UpdateCoverPosition( ) function. I added it as an idea if it is necessary. Edit: One may ask why I did not use a popup window for the entire GUI. Because I liked the 3-D like effect and the drop shadow of GUIs created in Windows 11. and a popup window does not have these features. #include <GUIConstants.au3> #include <WinAPIGdi.au3> Global $guiWidth = 320, $guiHeight = 100, $barColor = 0x198CFF Global $hGUI, $borderWidth, $barHeight, $GUIPos, $ClientPos Global $hCover, $idMinimize, $ctrlClose, $hRgn, $aMsg, $sMsg $hGUI = GUICreate("", $guiWidth, $guiHeight, -1, -1, $WS_OVERLAPPEDWINDOW) $GUIPos = WinGetPos($hGUI) $ClientPos = WinGetClientSize($hGUI) $borderWidth = ($GUIPos[2] - $ClientPos[0])/2 $barHeight = $GUIPos[3] - $ClientPos[1] - $borderWidth $hCover = GUICreate("", $ClientPos[0]+1, $barHeight, $GUIPos[0]+$borderWidth, $GUIPos[1]+1, $WS_POPUP, -1, $hGUI) GUISetBkColor($barColor, $hCover) GUISetFont(12, 400, 0, "Arial") GUICtrlCreateIcon("user32.dll", 101, 5, 5, 20, 20) GUICtrlSetResizing(-1, $GUI_DOCKLEFT+$GUI_DOCKSIZE) GUICtrlCreateLabel("Colored Bar Example", 30, 7, 160, 20) GUICtrlSetResizing(-1, $GUI_DOCKLEFT+$GUI_DOCKSIZE) $ctrlClose = GUICtrlCreateLabel("X", $guiWidth-40, 1, 40, $barHeight, BitOR($SS_CENTER, $SS_CENTERIMAGE)) GUICtrlSetBkColor(-1, $barColor) GUICtrlSetColor(-1, 0x404040) GUICtrlSetResizing(-1, $GUI_DOCKRIGHT+$GUI_DOCKSIZE) GUISetState(@SW_SHOW, $hCover) GUISetState(@SW_SHOW, $hGUI) If @OSVersion = "WIN_11" Then ; Create round corners for $hCover $hRgn = _WinAPI_CreateRoundRectRgn(0, 0, $ClientPos[0]+1, $barHeight+10, 13, 13) _WinAPI_SetWindowRgn($hCover, $hRgn) _WinAPI_DeleteObject($hRgn) EndIf GUIRegisterMsg($WM_WINDOWPOSCHANGED, "WM_WINDOWPOSCHANGED") AdlibRegister("_ColorButton", 100) While 1 $aMsg = GUIGetMsg(1) $sMsg = $aMsg[0] Switch $aMsg[1] Case $hCover Switch $sMsg Case $ctrlClose ExitLoop Case $GUI_EVENT_PRIMARYDOWN ; Click and drag $hCover DllCall("user32.dll", "int", "SendMessageW", "hwnd", $hCover, "uint", $WM_NCLBUTTONDOWN, "wparam", $HTCAPTION, "lparam", 0) EndSwitch EndSwitch WEnd Func WM_WINDOWPOSCHANGED($hWnd, $MsgID, $wParam, $lParam) ; Sync movement of $hGUI and $hCover #forceref $MsgID, $wParam, $lParam Switch $hWnd Case $hCover Local $aPos = WinGetPos($hCover) WinMove($hGUI, "", $aPos[0]-$borderWidth, $aPos[1]-1) Case $hGUI UpdateCoverPosition() EndSwitch Return $GUI_RUNDEFMSG EndFunc Func _ColorButton() ; Change background color of buttons when the mouse is over them Local $aArray = GUIGetCursorInfo($hCover) If $aArray[4] = $ctrlClose Then GUICtrlSetBkColor($ctrlClose, 0xC42B1C) GUICtrlSetColor(-1, 0xFFFFFF) Else GUICtrlSetBkColor($ctrlClose, $barColor) GUICtrlSetColor(-1, 0x404040) EndIf EndFunc Func UpdateCoverPosition() $GUIPos = WinGetPos($hGUI) $ClientPos = WinGetClientSize($hGUI) WinMove($hCover, "", $GUIPos[0]+$borderWidth, $GUIPos[1]+1, $ClientPos[0]+1, $barHeight) If @OSVersion = "WIN_11" Then ; Update round corners for $hCover $hRgn = _WinAPI_CreateRoundRectRgn(0, 0, $ClientPos[0]+1, $barHeight+10, 13, 13) _WinAPI_SetWindowRgn($hCover, $hRgn) _WinAPI_DeleteObject($hRgn) EndIf EndFunc

Thank you @argumentum 👌 . Then I will set the focus to current version v3.3.16.1 or newer. I will adjust the "test table" in the post #1 and in the README file. I don't have to use maps, no. But I really want to. The point about more then one database is a good one. At the moment it was not intended that way, but why not - thanks. Best regards Sven

Looked in "history of the changes to AutoIt v3" but there is no reference. Found it in my portable(s) v3.3.15.4 (Beta) but not in v3.3.14.5. Those versions are quite old. Should always focus in the current version. That been said, the use of maps has nothing to do with SQLite. Your "Func _Query()" in my view could be: Func _Query($sSQL, $hDB = -1) Local $aResult, $iRows, $iColumns _SQLite_GetTable2D($hDB, $sSQL, $aResult, $iRows, $iColumns) If @error Then _Log('_SQLite_GetTable2D() error') Return SetError(1) EndIf Return $aResult EndFunc and is more along the lines of what was ( in standard AutoIt3 ), to give an example. And is easy to use more than 1 DB in the script. But, if you need to use maps, then that's that I guess. "Warning: This feature is experimental. It may not work, may contain bugs or may be changed or removed without notice. DO NOT REPORT BUGS OR REQUEST NEW FEATURES FOR THIS FEATURE." "Remarks: Almost uniquely in AutoIt, keys are case sensitive - "MyKey" is not the same as "mykey" " That leads me to believe that if the one who coded that warns about "not too sure about this" and "Almost uniquely in AutoIt, keys are case sensitive", is that something in that library is questionable and/or conflict with the existing base of the AutoIt3 product. ..just as a side note. Most people in the forums are begging to remove the warning because it looks stable.

@orbs good test @CYCho this should fix it, by replacing Func WM_WINDOWPOSCHANGED with this one : Func WM_WINDOWPOSCHANGED($hWnd, $MsgID, $wParam, $lParam) ; Sync movement of $hGUI and $hCover #forceref $MsgID, $wParam, $lParam Switch $hWnd Case $hCover Local $aPos = WinGetPos($hCover) WinMove($hGUI, "", $aPos[0]-$borderWidth, $aPos[1]-1) Case $hGUI UpdateCoverPosition() EndSwitch Return $GUI_RUNDEFMSG EndFunc After that, you shouldn't need this part in main loop : ;~ Case $hGUI ;~ If $sMsg = $GUI_EVENT_RESIZED Then ;~ UpdateCoverPosition() ;~ EndIf

The information in the second bullet point of this post is probably what he's referring to.

I"ve currently very little free time yet I just had a quick look at the SQLite part. Setting PRAGMA busy_timeout = 2000; may be too short in practice. In multi-user context, this parameter should be way larger than the longest possible sequence of SQL statements transactions issued by the maximum concurent users, all of this as worst case. I can expand on this if needed. I set that to 10 minutes. Why do you make the IDs autoincrement? Don't, unless you really have a compelling reason to do so.

Done