# ICV range constraint not scaling

**URL:** <https://community.stardog.com/t/icv-range-constraint-not-scaling/1125>\
**Category:** Support\
**Created:** [July 6, 2018, 6:53am UTC](https://community.stardog.com/t/icv-range-constraint-not-scaling/1125 "2018-07-06T06:53:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hmottestad](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/hmottestad/32/19_2.png) [@hmottestad](https://community.stardog.com/u/hmottestad)\
**Post date:** [July 6, 2018, 6:53am UTC](https://community.stardog.com/t/icv-range-constraint-not-scaling/1125/1 "2018-07-06T06:53:13Z")

</div>

Hi,

I have the following type of ICV rule in our database: `range(arkiv:opprettetDato, xsd:dateTime)`

We have at the moment some 300 000 triples with arkiv:opprettetDato and the query for validating the ICV rule above takes around 400-500 ms.

Query is along the way of:

```auto
select distinct * where { 
    ?a arkiv:opprettetDato ?b. 
    filter(datatype(?b) != xsd:dateTime)
}

```

I don’t think there is much hope for getting that query to run any faster, so I’ve had to simply remove this ICV constraint from our database.

Any chance though that a specialised index just for this kind of case could be created?

Håvard

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/e/ed66b48a616f505106a4acde3c9cee7e6da9bc67.svg) [@system](https://community.stardog.com/u/system)\
**Post date:** [July 20, 2018, 6:53am UTC](https://community.stardog.com/t/icv-range-constraint-not-scaling/1125/2 "2018-07-20T06:53:19Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.