Post reply

Error converting data type varchar to bigint.

  • July 8, 2022 at 9:43 pm

    #4060853

    Almost certainly not a factor in case statement/null logic, but...

    varchar Column lengths are suspicious -- all varchar(50) in OptionsetMetadata  & varchar(255) in account. Are those really the column lengths used? Why? They seem questionable/problematic if data in varchar(255) columns ever exceed 50 characters allowed in the other table.

    Why are you taking columns that are varchar(50) in one table and varchar(255) in the other & casting them to varchar(100)? In  order to compare at all, they'd better never be longer than 50 characters.

    CREATE TABLE OptionsetMetadata (
        ...
        ts_primarysecondaryfocus varchar(50),
        ...
        ts_ukrow varchar(50),
    CREATE TABLE account (
        ...
        ts_primarysecondaryfocus varchar(255),
        ...
        ts_ukrow varchar(255),

     

  • July 8, 2022 at 10:32 pm

    #4060860

    Why did you delete your code

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply