Post reply

TRY_PARSE

  • April 4, 2018 at 9:48 am

    #336954

    A look at this new T-SQL function, along wiht some examples of where this can help prevent errors in code

  • April 11, 2018 at 3:55 am

    #1986287

    As this one goes hand in hand with the TRY_CONVERT I guess it makes sense for me to pick this one up as well - if you're happy with that?
    Cheers,
    Matthew.

  • April 11, 2018 at 9:01 am

    #1986368

    Take it

  • April 11, 2018 at 9:05 am

    #1986370

    Cheers

  • May 23, 2018 at 7:01 am

    #1991600

    I've been making a start on this one.

    It seems like the PARSE function hasn't rececived a lot of love in the blogosphere, can't find a single article going into any depth about why it is useful. I think it would be of benefit to go into some detail on this before introducing the TRY_PARSE, not sure whether that works better as one post or two. Alternatively, I could give TRY_PARSE brief coverage after introducing PARSE, but then refer to the TRY_CONVERT post as it's similar once you understandf PARSE.

    The main disadvantage of making it two posts is that the TRY_PARSE one will be very similar to the TRY_CONVERT post.

    Any thoughts?

    Thanks

  • May 23, 2018 at 9:02 am

    #1991641

    Having similar articles is fine. I think this should be two parts. There will be people that know one and not the other, so no need to get them to work through a long piece.

  • May 24, 2018 at 2:48 am

    #1991749

    Thanks

  • June 19, 2018 at 7:56 am

    #1994456

    I've submitted the article on PARSE, will work on TRY_PARSE next.

  • August 28, 2018 at 8:44 am

    #2003612

    I've now submitted the TRY_PARSE article, sorry it took so long.

  • August 28, 2018 at 11:34 am

    #2003668

    Thanks, and no worries. I'll get to it as quick as I can.

    Locking this thread for now.

Viewing 10 posts - 1 through 9 (of 9 total)

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