I could not find any document on how to use docuementdb geospatial query using azure function using nodejs:
SELECT *
FROM Areas a
WHERE ST_WITHIN({'type': 'Point', 'coordinates':[31.9, -4.8]}, a.location)
DocumentDB provides support for geospatial queries. You can find the documentation here. You can use the queryDocuments() function in the node.js SDK found here.
Built in binding support for DocumentDB queries is coming soon, but is not yet released. We just wrapped the work up (see issue here in our repo for details). Once this is released, there will be a new sqlQuery binding property that you can set, with full query parameter support, etc.
Related
I want to use the OData function SubstringOf in our filter expression. As of now I do not see any relevant api against GeneratedEntityName.PROPERTYNAME.
Is there a workaround to use substringOf incase the API is unavailable.
Using Java SAP Cloud SDK version 3.7.0
Unfortunately the feature you are requesting is currently not implemented. Due to dependency restrictions the SAP Cloud SDK will not be able to provide a native solution to use custom filter expressions.
new DefaultGeneratedService()
.getAllEntities()
.select(Entity.PROPERTY_NAME)
.withQueryParameter("$filter", "substringof('SAP', CompanyName)")
You will not be able to use other filter expressions by the VDM. So you have to construct the query string yourself.
We are planning to enable custom and type based filters sometime this year.
Is it possible to use Loopback 3.x with azure Cosmos DB (assuming I don't want to create my own connector)? I tried https://www.npmjs.com/package/loopback-connector-cosmosdb which isn't officially supported and I couldn't get it work. I have been looking for a quick way to set up an API on Azure (honestly I prefer SQL over CosmosDB but it seems like the simpler way to go) using NodeJS and haven't come across one yet. I started coding serverless functions for my API which work wonderfully except that adding authentication seems like a total drag and goes over my head completely. I indent to create both a web app and iOS App for what I'm developing any suggestions would be great!
This page describes the supported connection string properties for MySql Connector / .Net.
Which of these options are officially supported when connecting to MemSQL?
I suspect that options like SharedMemoryName and BlobAsUTF8IncludePattern are not. However, I couldn't find any official documentation for it.
I found some of the links which can help you identify your answer in the latest version of Singlestore 7.8 (on premises). However, i saw few special options in singlestore connector/.Net official documentation.
Link related to .Net/C# Connection for concurrent multi insert official documentation.
Go thru the above links from SingleStore's official documentation for more .Net connection related information.
Could you please help with what is better where Entity Framework or normal Sql query, I personally would like to use Entity Framework with Linq to SQL however I faced certain challenges today like there is no .ToList() or .FirstOrDefault() option available and also there are compatibilty issues using Entity Framework with .net Standard 2.0, so, anyone experienced the same and help what would be better approach.
According to your description, you need to using the namespace of System.Linq
.ToList() or .FirstOrDefault() option is available at .NET CORE 2.0 and these two method are extension methods under System.Linq. So we need to use System.Linq
namespace.
We can see below screenshot of my project.
I'm trying to test a new OData v4 web API I'm building with Excel and LinqPad but I'm getting the following error:
The required attribute Relationship is missing
The API seems correctly built, but "Relationship" never turns up in metadata, no matter how I structure the model.
What's going on? I'm sensing that v3 and 4 are not compatible.
PowerQuery does not yet support OData v4. You can harrass the development team here: :)
https://social.technet.microsoft.com/Forums/en-US/2169958f-9e2a-4fc2-a844-c0dce4c17a19/support-of-odata-v40?forum=powerquery
LinqPad's driver is clearly v3, but a search on linqpad.net reveals no mention of v4.