You can convert an integer to a float. You can also convert a float to an integer, and the data will not be lost or deleted. However, you will not be able to retrieve the values. Once you use float values, you have to keep them as floats.
You can convert a string to an integer or float and vice versa, as long as you do not change the format or add special characters.
Some data types, such as unique identifier (UID), geographic location (geo), boolean values, passwords, and datetime values, cannot be converted to other data types. And generally not possible to convert a list back to a single value.
You can only “play” with indexes (tokenizers) and directives. Directives are simply functions that are applied on the fly.
it is best to choose a data type that is appropriate for the values being stored and to avoid unnecessary conversions.
I cannot give you detailed information on what happens because I do not have complete knowledge of the code. I only know what is abstract or stated in Manish’s paper.
There is no “
@search” in DQL, only in GraphQL. Although it does the same thing as “
@index”. It is good to keep them separated. As far as I understand, you were referring to Dgraph and not GraphQL.
Yes, index changes are made in the background.
If you change or remove an index, the index will be removed or unavailable during the change. The data will still be there, but the index table will be removed and will not be available for querying. I’m not sure what specific impact you are referring to. As I mentioned before, removing an index can have a direct impact on the performance of some queries that are heavily reliant on indexing. It may cause these queries to run slower or even fail if the necessary index is not available(e.g regex).
As far as I know, it is immediate.
The question is. Why you bother with this? Are you planning to do changes all the time? I have some ideas about having multiple versions of the schema as if they were “branches”. I think it would be useful for someone who intends to make continual changes to DB indexes.
BTW, only the single predicate is impacted. If you use best effort, I believe it will not influence the query.
Yes. But there is no formula for how much you are able to measure.
Yes, but be careful. As I said, not every type of you will be able to do this.
It’s allowed. The opposite that sometimes can be bad. May generate errors due to float size.