• dan@upvote.au
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    That’s the employer’s fault for making it so easy to connect to prod with read-write permissions. Not your fault.

    • Big P@feddit.uk
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      At my last job I was given write permissions to production and I asked for read only credentials instead, I know my own stupidity

    • Chahk@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      Oh there was plenty of blame to go around. I wasn’t exactly fresh out of school either. I had “extensive experience with SQL Server” on my resume by then.

    • jjjalljs@ttrpg.network
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      +1

      We have read only access.

      Also transactions are good ideas.

      Also my database tool (the one built into pycharm) warns and requires you to hit submit a second time if you try a delete or update without a where. Discovered this on local where I really did want to update every record, but it’s a good setting.

      • Chahk@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        Look at mister fancy pants over here with a database tool. Back in my time we had to use Query Analyzer uphill both ways.