It took me awhile to nail this one as I thought my data was bad or the db was corrupt.
I’m using GUIDs as my primary ID data types. I imported the data from csv files and started to test the queries. Occasionally a query would not return data when I thought it should. It turns out that some apps/databases convert the letters in GUIDs to lowercase but I imported them as uppercase. In my testing I grabbed some GUIDs from another DB where I know the proper relationships were in place and it should give me some good results.
So this value works:
but this does not:
and returns this error:
Failed to convert user vertex id for parameter inputVoter
My experience is that all apps and databases consider upper case and lower case GUIDs to be the same, but I’m guessing that TG sees this as a string and TG is case sensitive. It would be nice if TG could add a GUID data type to it’s list of types and then consider both upper and lower case GUIDs to be the same. If an application is interacting the data coming going from different sources its likely there will be both upper and lower case GUIDs in the mix.