Signin Signup

Parameterized queries

This post was last updated for 369 days ago, and the information may already be changed

Hello,

I would like to be able to use an attribute of the parent block when writing an SQL query in an embed block. For the sake of example, consider I am in the document Trip to the Moon​ and I want to make a query that collects links to it. I would write

select b.* from blocks as b where b.content like "%trip to the moon%" order by updated desc

But I am already in Trip to the Moon​ (a document or a parent block with that name), so ideally I would like to grab the current document's title/name. I would like to replace the literal string "%trip to the moon%"​ with something like :parent.title​. How can I achieve this?

‍

    1 Follow
    9 Reply
    4
    3
    1.0k 106 42 260 628

    Related articles

    9 Reply
    Parameterized queries

    Welcome to here!

    Here we can learn from each other how to use SiYuan, give feedback and suggestions, and build SiYuan together.

    Signup About
    Please input reply content ...
    • ciwoyipang • • 2

      You can use the Query Widget which will automatically bring out the path

      image.png

      image.png

      image.png

      1 Reply
    • alvorithm •
      VIP Warrior Author

      Dear @ciwoyipang, thank you so much for making me aware of the query widget. It is a very featureful extension. But I think I did not describe my need clearly. What I am after is that the query block asks its parent for the text "trip to the moon", i.e. that string in the query should be generated automatically from the context.

      select * from blocks as b where b.content like "%insert here the title or the name of the parent block%"

      So if I put this query inside a document named "The mother of all queries" it would automatically fill in the value and execute

      select * from blocks as b where b.content like "%The mother of all queries%"

      Do you have an idea on how to customize queries based on the context of the query block (e.g. the parent, or the preceding block)?

      image.png

      PS. in order to have the type column values translated, is it necessary to do it in Siyuan or in the widget code?

    • alvorithm •
      VIP Warrior Author

      Hi again,

      I am wondering if using Javascript in the embed block could help here. Because I only get a partial translation and I don't know JS, I don't follow much of what is discussed in the feature request with issue number 9648, proposed by @frostime

      @frostime -- wout be possible to dynamically acquire metadata from the environment (current notebook/doc, preceding block, enclosing superblock) for use in a query by using the new //!js embed functionality?

      1 Reference
    • alvorithm •
      VIP Warrior Author

      Hi,

      Tagging @zuoqiu as well (author of widget-query?).

      Reading the documentation of the widget and exploring the Refs table (use the source 😉 ), I have come up with the following SQL query

      SELECT src.* FROM blocks AS src WHERE src.id in
	(SELECT refs.block_id from refs 
		WHERE refs.def_block_id='.block{.root_id}');

      This actually does what I want, i.e. it lists all the blocks pointing to the query's root block (in this case, the doc that contains the query). But

      1. widget-query renders the output as a table. I would like to render the blocks normally. Is there a way to do it like in embed block queries?
      2. alternatively, I could in principle use the same query in an embed block. But when I do, this produces no results. My question here: is the dot syntax .block{.root_id} that accesses properties of the current block not allowed in normal embeds @88250 ?

      I have searched extensively but so far I haven't found a comprehensive documentation of the query system, though I am thankful to @leolee9086 for sharing some examples in the forum.

      Please let me know if you find ways to improve my query above!

      Thank you everybody for your patience, and apologies that I just discovered the forum has a threaded reply function.

      Á.

      edit:

      1. changed = to IN in query so as to be able to list multiple incoming links.
      2. simplified the nested query, blocks as def not needed for it
      1 Reply
      2 Operate
      alvorithm updated this reply at 2023-12-21 01:10:59
      alvorithm updated this reply at 2023-12-21 01:06:30
    • ciwoyipang •

      思源 SQL 新人指南：SQL 语法 + Query + 模板 - 链滴 (ld246.com)

      SQL&Query 用法记录 - 链滴 (ld246.com)

      The above are two high-quality introductory articles from the Chinese community, which you may find readable using a translation tool.

      1 Reply
    • Knuex •
      PRO

      The LianDi site requires you to be registered to view it. And to register, it requires a mobile number.

      Is there any way to view that page without registering? @88250

      2 Reply
    • 88250 •
      MOD

      We are very sorry. Due to some security reasons, LianDi cannot be accessed without logging in.

    • ciwoyipang • • 1

      SQLQuery 用法记录.sy.zip
      思源 SQL 新人指南 SQL 语法 Query 模板.sy.zip

      The attachment is the exported original text, which can be directly imported.

      Then use the browser opening function of Siyuan to use translation tools

    • ciwoyipang •

      In addition, the embedding blocks of the ontology support JS.You can use plugins to enhance embedded block queries.

      siyuan-plugin-data-query

      image.png

    Please input reply content ...
    alvorithm
    Reply
    9
     Article
    4
     Point
    928

    Recent hot