Closed WolfgangFahl closed 2 weeks ago
Can you please dump the entire schema of the database? e.g. echo ".schema" | sqlite3 /path/to/file.db
Or attach the problematic database?
Or provide steps to reproduce?
This is basically nothing for me to work with.
@coleifer - certainly - this is a database with invalid views which happens since it is in development. I would love to use sqlite-web to drop the invalid views and create working new ones.
echo ".schema" | sqlite3 BITPlan.db
CREATE TABLE Posting(Buchungstag TEXT,Konto TEXT,Vorgang TEXT,Empfänger TEXT,Verwendungszweck TEXT,Kategorie TEXT,Klasse TEXT,Betrag TEXT,isodate TIMESTAMP);
CREATE VIEW BuchungF AS
SELECT
isodate,
Betrag as amount,
Konto as account,
Kategorie as category,
Verwendungszweck as purpose,
'Empfänger' as receiver,
Vorgang as action,
Klasse as class
FROM Posting
ORDER BY isodate DESC
/* BuchungF(isodate,amount,account,category,purpose,receiver,"action",class) */;
CREATE VIEW Buchung AS
SELECT
isodate,
Amt as amount,
AmtCcy as currency,
OwnrAcctNo as account,
Category as category,
RmtInf as purpose,
RmtdNm as receiver,
BookgTxt as action,
Notes as class
FROM Posting
ORDER BY isodate DESC;
Thank you for the extra info, this definitely helps me understand. Unfortunately, I don't think there's much I can offer in the way of help. What am I supposed to show for a totally broken view/schema? You'll need to drop those views from the sqlite shell.
In mediawiki there is the concept of a "red link" that is the View would be shown in red with the textual info about the schema and the error message but no details. A drop would be offered as a remedy. This is exactly what i had hoped this issue would turn into as a feature request. The difference is that i would still be able to query the valid table and not be left in a state where i can no start the software at all.
see #31
it would be great if sqlite_web would react more robust on such errors so that the database can still be inspected.