David Beroff (d4b) wrote,
David Beroff
d4b

Woof! ... INSERT (human characteristics) ... WHERE NOT EXISTS

As usual, I'm learning from my outsourcing effort, and I came to the realization that we need to replace the INSERT ... ON DUPLICATE KEY UPDATE code with the more appropriate INSERT ... WHERE NOT EXISTS code instead.

Also, I realized today that, in an effort to streamline the process of joining and then using AboutTh.is, Members don't necessarily have to set their primary and additional languages in advance. I wrote some triggers which make the reasonable assumption that the first language the Member uses to express an Opinion is their primary language, and if they use additional Opinion languages after that, those are added to the Member's Fluency set. The Member will be able to configure these later, as well, but the point is that they won't have to.

Of course, even reporting a language at all won't ever be a requirement, (and thus stored internally as und as per ISO 639-3), but it'll sure be rather helpful. :-)

In a related tangent, is the ISO 639-3 generic code zxx (for non-language sounds such as those made by animals) an example of speciesism, i.e., prejudice against non-humans? :-)
Tags: advertising, mtat, outsourcing, webdev
Subscribe

  • Business begets business

    I got three more voice acting jobs since I last posted, with another one in the wings. I've become pretty convinced that the algorithm that Upwork…

  • Generating PDF's on-the-fly

    My investment firm client asked me for the ability to have their Members print current stock certificates from the database and the website,…

  • "This button does nothing"

    Yeah, I should be blogging more, but there's some sort of Law where, when you're trying to break away to go on vacation, that's the precise time that…

  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 0 comments