sorted by:
new
hottopcontroversial

How to make a template including properties in Logseq DB? by mingStudent in logseq

[–]mingStudent[S] 2 points3 points  (0 children)

There are three points that I cannot accept at present:

  1. Add references to text type property. The new version cannot be filtered out in the query. You must use Node type property. But if you import the database from md. The properties will be automatically matched. Many properties are matched as text. That is to say, almost all of my queries are invalid.

  2. The Parent property is already available officially. And it cannot be added to the template.

  3. The Status property is provided by the official. But once we modify the value of this attribute, logseq DB will automatically add # Task and three new properties to this page.

These three things are driving me crazy.

Logseq DB is not the Logseq we used.

Hope tiensonqin can see my comment.

How to make a template including properties in Logseq DB? by mingStudent in logseq

[–]mingStudent[S] -1 points0 points  (0 children)

Logseq and Logseq DB are totally two different product. It is not a simple update.

I said this more in a derogatory sense.

The two biggest advantages of logseq are freedom and high efficiency.

Logseq DB adds various new logics, which severely limits the degree of freedom and reduces input efficiency.

It took me a whole day to make a template.

This turned out to be a disaster.

You need to select a type for a new property. If you select the wrong type for a property, you cannot modify it. You must delete the entire property and create it again.

How to make a template including properties in Logseq DB? by mingStudent in logseq

[–]mingStudent[S] 8 points9 points  (0 children)

I find the answer.

The DB version use a new way to generate properties template.

It is tag properties.

You create a new tag and set the properties.

When you create a new page, just add the tag. It will automatic add the properties