After initial start and new database created,
it works normal in current session.
But after closing neso, and starting again
there is no database list, always 'Create database'
button. There is no option to connect to
existing database.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Linked items
0
Link issues together to show that they're related.
Learn more.
yes, it is there: c:\users\<username>\.neso\3.0\demo.sqlite.
Similarly, I've installed Windows tryton client and trytond server on
Linux w/ sqlite as backend. Funny thing is that when adding connection profile,
it cannot list sqlite databases on the server, just Create Database.
But I can connect to the sqlite database if I enter server:port and database
name directly.
Having the same problem here.
But if I create a new databasem,connect to the new database and then select in
the menu to connect to another databse, then the neso client then finds the old
database.
To exist any way for to create neso.exe, from neso.py for test/hack in my pc,
using print another changes maybe I help, but I don't know how create neso.exe
correctly.
Just to confirm this issue only affects windows, as I can reproduce it on a
Windows VM machine, but not on my linux box.
Just installed a python shell on the Windows VM machine and I tried list dirs of
the folder and they are correctly listed, so the problem may be opening the
cursor to the database.
I also installed sqlite-cli on the windows machine and I can access the database
without problems.
Any tips about how to run neso from sources on windows, or how to create
neso.exe (as Oscar already pointed) will be great to solve the issue.
I executed more code and it fails in the test query, concrectly in [1]. I get
the following traceback:
Traceback (most recent call last):
File "C:\Program Files\neso-3.0.0\neso.py", line 150, in <module>
cursor2.execute(sql, params)
File "trytond\trytond\backend\sqlite\database.pyc", line 342, in execute
OperationalError: near "%": syntax error
Which is quite strange for me.
I also printed the generated query and params, which lead to:
('SELECT "a"."name" FROM "sqlite_master" AS "a" WHERE (("a"."type" = %s) AND
("a"."name" IN (%s, %s, %s, %s, %s, %s, %s, %s, %s, %s)))', ('table',
'ir_model', 'ir_model_field', 'ir_ui_view', 'ir_ui_menu', 'res_user',
'res_group', 'ir_module_module', 'ir_module_module_dependency',
'ir_translation', 'ir_lang'))
Indeed it was fixed in trunk with changeset 610cf1f6c946 but we can not backport
this patch because of API changes.
So here is a patch that re-use the old raw SQL string for 3.0