This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
First of all, let me just say that support for variable-width strings is on my '10 Things I Love about Alteryx'. Having just escaped from a FoxPro environment, I love the intuitive ways Alteryx deals with field sizes.
One wonkish question, though: what's the difference between v_string and v_wstring fields? Clearly the 'w' stands for 'wide', so there's probably a degree of optimization, but is there a max size for v_string fields, or something like that?
The only difference I see seems to refer to support for unicode characters. Is that it?
V_String: "If the string greater than 16 characters and varies in length from value to value."
V_WString: "If the string greater than 16 characters and varies in length from value to value. If the string contains unicode and is longer than 16 characters, use V_WString, such as a "Notes" or "Address" field."
Since V_WStrings support unicode, they require more bytes per character than V_Strings, so if you know that the data doesn't contain unicode characters, my understanding is that you should see a bit better/faster performance by using V_String instead.