Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: JDBC Node error on version 6.1.3

  1. #11
    Lavastorm Employee
    Join Date
    Aug 2009
    Location
    Cologne
    Posts
    513

    Default

    Hey, try the node in the attached BRG.
    So pull the data out of the DB in unicode, then run the result through the attached node.
    This will simply locate any unicode fields, in the input and attempt to encode them in the character set used by the string type.
    If there are any unmappable characters, they will be replaced by "?" characters.
    So the output will be exactly the same as the input, just with any unicode fields changed to string (with replacement of unmappable).
    Attached Files Attached Files

  2. #12

    Default

    HI Tim,

    Even though this graph is in a newer version than then 6.1.3 version I can work with this thank you as using this node around 400 times is going to be easier then converting over 4000 to cope with the changes.
    This is something that Lavastorm needs to look into as a change, even though i understand the reason behind the change some data can have multiple character sets inside text fields so we need the opportunity to turn this validation off if required.

    Regards,

    Keith
    Last edited by khopkins; 02-09-2017 at 10:39 AM.

  3. #13

    Default

    I'm having the same error on other JDBC nodes without any cast functions just select.
    Last edited by online; 01-23-2018 at 03:27 PM.

  4. #14
    Contributor
    Join Date
    Nov 2008
    Location
    Little Rock
    Posts
    5

    Default

    Glad to have found post. Problems here too. Hopefully there will be a permanent fix similar to Keith's suggestion.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •