msql | This is a tool for making build sql | SQL Database library

Thta is normal behaviour. instead of throwing an error and stopping all activities.

you get a warning and all following commands go ahead.

IF EXISTS is used to prevent an error from occurring if the database does not exist.

source

I fixed these issues to get the code to work:

• make the number of placeholders in the insert statement equal to the number of columns
• the placeholders should be lower-case '%s'
• the cell delimiter appears to be a semi-colon, not a comma.

For simply reading a csv with ~1000 rows Pandas is overkill (and iterrows seems not to behave as you expect). I've used the csv module from the standard library instead.

Solution: We cannot have multiple Foreign Key Names with the same name. I have changed the name and it worked.

""

This is a little tricky. Although Hive supports range window frames, it only supports them with numbers, not intervals.

So, you need to convert the timestamp to a number and then use that:

I found the bug. You created create_database window that is root_db window using

root = Tk() but Tk() can be used only 1 time. So the code is running but the variables you passed to the entry boxes are not working.

Solution

Just change.

For anyone who has the same problem: In the end, I was unable to find any way to execute the query that I wanted with reasonable performance.

This schema design is not the optimal way to execute such complicated queries. What I ended up doing was making the details array an object and have separate documents for separate details. And then I made a parent schema that kept reference of the details for the same estate.

You can use reverse referencing or referencing according to the queries that you want to execute.

You made a good start on keeping your database code separate from you user interface code. However, any message boxes should be shown in the user interface and any sql statements should be written in the data access code.

I used Using...End Using blocks to ensure that database objects are closed and disposed. I used parameters to protect against sql injection. I am not too sure of the mapping of DbType types to Sqlite types. You might have to fool with that a bit. In you original Update statement you had the ID value in quotes. This would pass a string. When you use parameters, you don't have to worry about that or ampersands and double quotes. Just one clean string.

I believe your problems stem from the AutoCompleteMode. Suggest and SuggestAppend seem to fill in the text box as expected. Append seem to do nothing. I don't think this is working as intended.

I tested with a little database I have. It is Sql Server but should work the same for Sqlite. I used a bit of Linq magic to get the AutoCompleteCustomSource. A few other changes... Using...End Using blocks ensure that database objects are closed and disposed. You don't need a DataAdapter, just a DataTable and Command.

I think the problem is here:

Authserver listening to 0.0.0.0:8085

You changed the default port of the authserver process to 8085. That's supposed to be the port of the worldserver instead.

The client uses by default the port 3724 so that should be the port you should set as RealmServerPort of your authserver.conf configuration file.