You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that GetAsync throws a POST 409 error. This means that the table or record already exists.
I believe a GET should not use a POST. If the table does not exist, should that not result in a 404 instead? Or something like this? Using a GET which creates a table which would then return 0 results because the table has no items seems pointless.
It's very annoying to see this error in my logs because at first sight it looks like something is going wrong, but nothing is.
I believe this error could occur thanks to the EnsureTable method which uses a CreateIfNotExists method which can cause the POST. The table already exists though, so I don't know why a POST is used.
I'd like to see a solution where this error does not occur :)
The text was updated successfully, but these errors were encountered:
Hello!
I have noticed that
GetAsync
throws a POST 409 error. This means that the table or record already exists.I believe a GET should not use a POST. If the table does not exist, should that not result in a 404 instead? Or something like this? Using a GET which creates a table which would then return 0 results because the table has no items seems pointless.
It's very annoying to see this error in my logs because at first sight it looks like something is going wrong, but nothing is.
I believe this error could occur thanks to the
EnsureTable
method which uses aCreateIfNotExists
method which can cause the POST. The table already exists though, so I don't know why a POST is used.I'd like to see a solution where this error does not occur :)
The text was updated successfully, but these errors were encountered: