Recent changes to bugs

#28 after fresh install, sqlite access fails

Jose Silva — Thu, 27 Feb 2025 10:22:21 -0000

I also can't use it after installation. I did the same thing, copied that file and copied it to the indicated folder.

When I log I take that:
VERSÃO 0.99.5
Aviso!
Você está tentando efetuar login através do grupo padrão . Se você estiver fazendo login pela primeira vez, isso está correto; Entre em contato com o administrador do sistema para definir os privilégios corretamente
Mesas disponíveis
No momento não há tabelas disponíveis Inicializar registro

It didn't work.
I noticed that the database is empty, with no tables or records.
How can I populate the database? Where can I find the .sql file to import? Is that the way it works?

We appreciate any information, Thank

postgres issue - Synchronize database/frontend fails when CaseSensitive table names are found

K P — Wed, 05 Aug 2020 09:46:01 -0000

In postgres, "Synchronize database/frontend" fails when CaseSensitive (i.e. schemaname.PREFIX_tblname) table names are found.
The error returned is:
ERROR: relation "schemaname.prefix_tblname" does not exist

(note that "PREFIX" has been converted to lowercase in the error, which is where it crashed).

Unfortunately some other program decided to create a bunch of tables with a capitalised prefix in my schema (instead of creating its own schema or something), and to make sure it stayed capitalised, it also quoted it during creation.. now it has to ALWAYS be quoted when used in various places.

the fix was easy enough, changing class.ischema_postgres.php file, line 202 as follows.
from:
WHERE c.oid = (SELECT '{$db1['dbname']}.$table'::regclass::oid)
to:
WHERE c.oid = (SELECT '{$db1['dbname']}.\"$table\"'::regclass::oid)

will keep updating this ticket if my DB breaks other places in the application...

specifying input type "values defined by table" generates PHP warnings

clifford harrison — Wed, 08 May 2019 11:42:38 -0000

Warnings:
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\SQLProcessor.php on line 142
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\SQLProcessor.php on line 170
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\SQLProcessor.php on line 173
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\SQLProcessor.php on line 276
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\SQLProcessor.php on line 365
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\FromProcessor.php on line 161
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\FromProcessor.php on line 183
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\FromProcessor.php on line 189
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\FromProcessor.php on line 213
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\Apache24\htdocs\vfront\plugins\php-sql-parser\src\processors\ShowProcessor.php on line 70

Configuration:
Milestone: 0.99.5
OS: Windows 10
Apache Version: Apache/2.4.39 (Win32) PHP/7.3.4 OpenSSL/1.0.2r
PHP version: 7.3.4
Database version: 10.3.10-MariaDB (Mysql 5.7 equivalent)

Thank you for your fabulous software.

misleading error message in installation routine

Rolf — Sun, 17 Feb 2019 16:25:20 -0000

There is an error in the installation routine. Vfront complains that vfront-code/files directory is not writeable when in fact it was. The problem was subdirectories within that directory were not writable. Please update the wording on the error message.

Thank you for your work.

#31 Records not view in grid table

Pongracz Istvan — Wed, 18 Oct 2017 19:56:16 -0000

I reinstalled VFront, now the VFront tables are in the same Postgresql database as the DB itself.
Now when I imported the DB into the frontend, the Compatibility test showed only 4 errors instead of 12 (no primary keys).

So, in general, it seems using sqlite as vfront backend is not really a good idea.

Note: I had to increase the size of commento (varchar 255) in all vfront tables, otherwise I was not able to import the DB. This is because I had heavy comments on the tables.

#31 Records not view in grid table

Pongracz Istvan — Wed, 18 Oct 2017 17:53:50 -0000

In other table VFront was able to see the Primary Key.
The difference could be, the problematic table has foreign key, too.
Here are the constraints:

CONSTRAINT msz_id_pk PRIMARY KEY (id),
CONSTRAINT fid_fk FOREIGN KEY (fid)
REFERENCES mf (id) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION

#31 Records not view in grid table

Pongracz Istvan — Wed, 18 Oct 2017 17:42:05 -0000

It seems VFront just cannot see the Primary Key of the table in Postgresql 8.4.
There is a primary key defined in the table, but VFront cannot see it.

#31 Records not view in grid table

Pongracz Istvan — Wed, 18 Oct 2017 17:39:52 -0000

Some progress:
VFront has log, where I can found some leads.
It seems the missing Primary Key is the reason, why the grid view is empty, at least in my case.

Here is the relevant part from the log:

LINE 1: SELECT  as pk, fsz,cd,vk,vn,vg,var...
                ^   SELECT as pk,

#31 Records not view in grid table

Pongracz Istvan — Wed, 18 Oct 2017 16:25:21 -0000

Hi,
This bug still exists in 0.99.5.
I have
Database is on Postgresql 8.4 (yes, old),
Vfront in sqlite
Table in the database has no primary key.
In the browser I cannot see any relevant issue (Shift+F8 devtools, console)

What can I do solve this issue?
What kind of info do you need to solve this?
Thanks,
István

Checkboxes do not update properly when using postgresql database

Matt Francis — Thu, 28 Sep 2017 14:15:45 -0000

. The variable PGdb was initialized incorrectly in scheda.php:

File: scheda.php, line 291

Incorrect: $PGdb= ($db1['dbtype']=='postgres') ? "true":"false";

Verfied fix: $PGdb= ($db1['dbtype']=='postgres') ? true:false;