Archimedes Trajano

I guess there should be an overload to support: 1. bind(Map.of(...)) 2. bind("param", param) 3. bind(TypedParam, param) Though the third one like I said I am not certain how that...

The problem with the third item is how do you know what the bind parameters are? They need to be parsed from the JPQL which is just a string inside...

I'm saying JPQL as in the string in createQuery is JPQL. But for you to get the `:param` text and generate a type-safe variable I don't think is possible. For...

@gavinking it's more the established name in the database community at large I guess.

@gavinking I still vote `bind` as it is the established term in the database community and that `setParameter` was a bad name to begin with ^_^

But can you make sure it doesn't throw an error about passing an int when it is expecting an int64 for tmpfs I think it's because of the size but...

> Hey, thanks for the issue! There are actually many options available (https://docs.docker.com/engine/storage/tmpfs/#options-for---tmpfs). I think adding all of them as single attributes to the `tmpfs_options` might be a bit cumbersome,...

It appears to be happening with the current store release as well https://help.nextcloud.com/t/does-nextcloud-memories-allow-modifying-the-coordinate-data-in-heic-files/226159/7

@NL-TCH which filesystempermissions are you talking of?

It appears to be a transaction issue ``` Debug no app in context Exception: dirty table reads: SELECT `path` FROM 2025-06-03T17:09:27+00:00 `*PREFIX*filecache` WHERE (`storage` = :dcValue1) AND (`fileid` = :dcValue2)...