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
It will be useful if query criteria can be specified (for example, querying active/drilling wells, etc.). Currently for many objects we have to fetch all.
The text was updated successfully, but these errors were encountered:
We will look into this, I guess a good question for you would be would you like to filter on the criteria that is commonly filtered on, as the criteria does differ from server to server. It would be helpful if you could provide a list of properties that you would like to query on so that we can support those first.
While the flexible constraint settings like in jwitsml might take some time to implement in this library, I agree for now it will be better to just focus on a list of commonly used filtering properties. For the first step, I will need to feed small requests into a scheduling system, so when querying log data, be able to set startDepth/endDepth/startDateTime/endDateTime will be necessary. Also, the filtering on well's status (active wells only, for example) is helpful too. I will provide more properties down the road of using your library.
It will be useful if query criteria can be specified (for example, querying active/drilling wells, etc.). Currently for many objects we have to fetch all.
The text was updated successfully, but these errors were encountered: