Azure Storage は 409 Conflict になったリクエストも課金対象なので、何も考えずに CreateIfNotExists を呼び出してたら課金も増えるし、意外に応答時間遅いからパフォーマンスも落ちる罠が

Blob Container / Queue / Table の CreateIfNotExists 呼び出しはやめて IaC レベルで存在することを担保するようにしないとダメ

Unser Kollege @th_p Thomas erklärt den Hintergrund der #CreateIfNotExists-Fehler bei der Nutzung von #AzureTableStorage und #ApplicationInsights und legt in seinem Artikel zwei Lösungswege dar, wie man ein mit Fehlern überladenes Protokoll vermeiden kann: medium.com/medialesson/appli…

I don't like both since they can carry a complicated set of rules, guaranteeUserExists is better but it kinda has the same problem. CreateIfNotExists tells you what's going to happen, so I don't need to check the rules of the method since they are spelled to me in the name.

É quando fazer uma coisa duas vezes (ou mais) tem o mesmo resultado de fazer uma vez. Um exemplo recorrente disso é os createIfNotExists(x) out getOrCreate(x) no backend, se tentar criar uma coisa que já existe ele não faz nada, e retorna o objeto

CreateIfNotExists will try to create the container and will silently eat the 409 exception raised by REST API if the container exists. FWIW, you should not be calling this & IfExists (as mentioned by @jongallant) every time you read the blob. 2 unnecessary network calls.

@laravelphp peeps - I know we have Schema::dropIfExists, but am I imaging we also have something like Schema::createIfNotExists? PR, I think, if we don't?

I'm not sure, but don't you get an error, when the table already exists, when you check the "success"? The manual say for the return value of "createIfNotExists": "true if the table did not already exist and was created; otherwise false ." docs.microsoft.com/en-us/dot…

laravelのSchemaでcreate以外にcreateIfNotExistsみたいなのないの

CreateIfNotExists throwing ArgumentNullExecption #azure ift.tt/2qzlxVs