Hello Richard !
I just looked at it and I have some doubts about the generated
parse.sql, as I see it there is this table:
CREATE TABLE symbol(
id INTEGER PRIMARY KEY,
name TEXT NOT NULL,
isTerminal BOOLEAN NOT NULL,
fallback INTEGER REFERENCES symbol
);
--and this entries
--..
Hello Richard !
My bad after writing the last reply I found that "EXPLAIN" and "explain"
are different symbols there.
Could a small comment be generated at the begin of the generated
"parse.sql" ?
Something like: (dummy example)
---
-- This is a generated output from lemon parse gen
Hello Richard !
Again after rereading your reply and trying to use the "parse.sql" I
noticed that it doesn't have a "begin;../commit;" wrapper as it's
recommended to not having "fsync" calls on each insert.
Cheers !
On 28/11/19 23:54, Richard Hipp wrote:
On 11/28/19, Laurent Dhont wrote:
Hello Richard !
Sorry by split my reply in so many small ones !
When trying to use the generate "parse.sql" I'm getting this:
sqlite3 parse.db < parse.sql
Error: near line 10: FOREIGN KEY constraint failed
Error: near line 11: FOREIGN KEY constraint failed
Error: near line 12: FOREIGN KEY
Dear Richard,
This has been very helpful, I have the parse.sql file. I feel very
flattered that you took the time to answer my question. My boss says you
are the one that should win a nobel prize.
This has been much appreciated!!
I completely understand if you won't answer anymore but I ca
On 11/29/19, Laurent wrote:
>
> Could you perhaps explain what pos means and what the [isTerminal] = 0
> rows mean.
>
New check-in enhances the output to include a comment in the SQL
before the encoding of each production rule. This should help make it
clear what the SQL is trying to represent.
On Fri, Nov 29, 2019 at 2:10 PM Richard Hipp wrote:
> On 11/29/19, Laurent wrote:
> >
> > Could you perhaps explain what pos means and what the [isTerminal] =
> 0 rows mean.
>
> New check-in enhances the output to include a comment in the SQL
> before the encoding of each production rule. This
Hello Dominique !
Here are two views that can bring that info to a query:
==
CREATE VIEW rule_list_view AS
SELECT
a.ruleid,
b.name,
a.lhs
FROM rule AS a
LEFT JOIN symbol AS b ON a.lhs = b.id;
CREATE VIEW rulerhs_list_view AS
SELECT
a.ruleid,
b.name as symbol_name,
c
8 matches
Mail list logo