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.name as rule_name,
a.pos,
a.sym
FROM rulerhs AS a
LEFT JOIN symbol AS b ON a.sym = b.id
LEFT JOIN rule_list_view AS c ON a.ruleid = c.ruleid;
======
Maybe others can contribute with other views to make the info there
easier to use !
Cheers !
On 29/11/19 14:56, Dominique Devienne wrote:
On Fri, Nov 29, 2019 at 2:10 PM Richard Hipp <d...@sqlite.org> wrote:
On 11/29/19, Laurent <dhontlaur...@hotmail.com> 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.
Hi. Why not add a column and write it to the SQL insert?
Rather than as a comment in the SQL "dump"? The first thing I'd do with
that new output file,
would be to run it to generate the DB, then look at the DB in a graphical
client, to side and dice
the data. As it stands, those useful comments would be lost in that
scenario. My $0.02. --DD
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
