#28 after fresh install, sqlite access fails

[Mateusz Viste]

I installed a fresh installation of v0.99.2. It's an installation that connects to a postgresql, and uses a local sqlite file for keeping internal settings of VFront. The problem I experience is this:

1. right after installation, I was unable to log in into VFront, all I was getting was an error message "Connection error: file does not exists, please check your conf file or your sqlite db". This relates to the fact that the sqlite file I declared in the configuration file wasn't existing. Here, I'd rather expect VFront to create this file automatically, instead of failing with the above error message.

2. I created manually the sqlite file by running sqlite3 from CLI. This created a 0-byte file. Then, VFront tries to run, but fail with the error "Database query problem". In error_logs, I see this:

[2015-10-08T07:02:32+02:00]     /index.php:48   intranet.border6.com (192.168.99.2)     <SELECT>        sqlite3 1       no such table: utente    SELECT * FROM utente WHERE nick='mateusz.viste' LIMIT 1

I understand that VFront is unable to find its config table inside the sqlite db, but again, I'd expect VFront to populate all it needs the first time it's called... Otherwise I don't really know what I should do now to make it work.

[Marcello Verona]

Hi Mateusz
Normally VFront, during the installation, copy the sqlite file from a template (_install/sqlite/vmsql.sqlite3.dist) to the_ files/db/vfront.sqlite_ file.

In your experience something goes wrong.
Will be interesting to know what, exactly. Have you other informations?