Great work Saseed! You are explaining the exact scenario what we faced. As you mentioned We never aware of this problem. You taught me not only how to use nvarchar with EF, we should always keep an eye on the all bugs and discussion in the repo. Thanks again and keep doing the great work. 👍
nice tip for ef core but don't use database for storing big file , SQL server design for fast and small request/response . file stream is good option for storing that as binary , also there is azurite (Azure Storage API) for free write on node.js . you can use that as well . tip: as much as you can don'tuse max on varchar or nvarchar .always have limit . nice work keep going.
Great work Saeed, keep continue 🙂
@@SamH-h1v Thanks and happy you like it
Great work Saseed! You are explaining the exact scenario what we faced. As you mentioned We never aware of this problem. You taught me not only how to use nvarchar with EF, we should always keep an eye on the all bugs and discussion in the repo.
Thanks again and keep doing the great work. 👍
Very happy it was helpful to you, please support me by sharing my videos to your network, would be appreciated 🙏
@@sa-es-ir I already shared to my network. 👍
nice tip for ef core but don't use database for storing big file , SQL server design for fast and small request/response . file stream is good option for storing that as binary , also there is azurite (Azure Storage API) for free write on node.js . you can use that as well .
tip: as much as you can don'tuse max on varchar or nvarchar .always have limit .
nice work keep going.
@@mahdiyar6725 Thanks for the great sum up and totally agree.
It's weird that still open
They mentioned in the ticket that it will take years to fix!!