SQLite Node & Credentials

[jan]

Welcome to the community @IsserTerrus!

Yes totally agree, that a node like it could be interesting for many use cases.

For your example use-case we had actually the following planned:

1. Create some kind of abstraction layer that allows nodes to read/write data to the database (it would use an own table in the database the one the user uses already anyway, so could be Postgres, SQLite, MySQL, …)
2. Create a node which allows to send in items, define a unique parameter (like id, date, …) and this node would then use what got created in 1, to see if that item got processed already earlier. If it did, it gets filtered out. If not, it passes through.

Btw. till that is in place you can use static-data. Here an example for actually exactly the same use-case:

How to get new RSS item?

Welcome to the community! Yes, the node simply returns all the items it finds. The filtering out of already processed items has to be done manually. That means you have to save the date of the last processed item and then remove all the ones before that date. It is possible to save that value in multiple ways, the easiest is with the static data. Here an example workflow: It is, however, important to remember that the static data does not get read and written when testi…