# Datatypes in SPARQL UPDATE

**URL:** <https://community.stardog.com/t/datatypes-in-sparql-update/1735>\
**Category:** Bug\
**Created:** [June 12, 2019, 5:01pm UTC](https://community.stardog.com/t/datatypes-in-sparql-update/1735 "2019-06-12T17:01:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/stephen/32/27_2.png) [@stephen](https://community.stardog.com/u/stephen)\
**Post date:** [June 13, 2019, 2:24pm UTC](https://community.stardog.com/t/datatypes-in-sparql-update/1735/2 "2019-06-13T14:24:38Z")

</div>

Hi,

There is actually another thread in which we detail what's happening here: [Datatype handling](https://community.stardog.com/t/datatype-handling/1540)

The short version is Stardog canonicalizes literals by default to improve query and loading performance. If you require literals to be stored exactly as specified, you can set index.literals.canonical=false when creating your database.

---

_[View the full topic](https://community.stardog.com/t/datatypes-in-sparql-update/1735)._