Error can not create `tablesdb` event with the UI and CLi

When i'm trying to add an event with tablesdb i get an error message

My event value: tablesdb.mtg-decklist-dev.tables.queue_parsing.rows.*.create

Same error with the CLI:
✗ Error • process-parsing-queue (process-parsing-… • Invalid events param: Value must a valid array no longer t (it's crop i don't know why)

I've try with the old value databases and it's working
old event value:databases.mtg-decklist-dev.tables.queue_parsing.rows.*.create
Also in UI, the form automatically add databases (in the appwrite v1 and v2.beta)

Error can not create tablesdb event with the UI and CLi

@Luke maybe you can help me 🙂 it's follow my works on function that we have speak in MP

Hey @Horsty - Cyril - MagicTools the value you found working is actually the correct one, not a workaround.

databases.mtg-decklist-dev.tables.queue_parsing.rows.*.create

The TablesDB API was renamed, but the event namespace stayed databases. So the prefix is always databases., even for TablesDB, while the rest of the path already uses the new nouns (tables, rows). There's no tablesdb event namespace at all, which is why the validator rejects it outright.

So the Console prefilling databases is doing the right thing. 👍

I'll discuss with the team why tablesdb exists everywhere else (service name, URL path, DB type) but not as an event namespace, guessing it is completely reasonable, and you just get a silent 400.

also the docs shows tablesdb now instead of databases for events as well

https://appwrite.io/docs/products/functions/execute#events

We have merged in a fix, should be released soon

Ok thanks for this messsage
And yes the docs is missleading about it 🙂

So @Luke I présume I have another issue because I have the right event setup, but it’s not fired I don’t understand why and it’s very difficult to debug it

I will setup something to have more info about it

i'm wondering if it's a similar thing with the list databases.

• /v1/tablesdb returns all databases
• /v1/databases returns only the type: legacy databases (the type is not related to the db type visible in the console)

so maybe it's the same with events, using databases.* only trigger for type: legacy databases and not type: tablesdb ?

If possible @Horsty - Cyril - MagicTools, can you list your databases and tell us in the API response, what does it shows for the type if it's tablesdb that might be why

https://discord.com/channels/564160730845151244/1529847339873861662

i will test this, but actually my tables has type "tablesdb"

can you check in the devtools response ? in the UI they all shows as TablesDB

i will check tonight, i don't have time for the moment