Notices

1. Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Friday, 07-Sep-2018 11:24:57 CEST Ekaitz Zárraga 👹

   • .:Ninjatrappeur:.

   @Ninjatrappeur

   > properly catch database exceptions

   Haha

   FUCK NO.

   xD

   • .:Ninjatrappeur:. (ninjatrappeur@social.alternativebit.fr)'s status on Friday, 07-Sep-2018 11:25:02 CEST .:Ninjatrappeur:.

     in reply to
     @ekaitz_zarraga Héhé, no logging, no exception catching in either my external compiler calls nor DB calls.
     
     Why setup everything properly when you can procrastinate this until a week before the deadline :D
     Ekaitz Zárraga 👹 repeated this.
   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Friday, 07-Sep-2018 11:28:08 CEST Ekaitz Zárraga 👹

     in reply to

     • .:Ninjatrappeur:.

     @Ninjatrappeur I'm making a website now and I'm handling *SOME* exceptions only. Not all of them.

     Because... y'know...
     Also because I've seen other people doing the same. There's a precedent, so I don't feel bad about it.

   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Friday, 07-Sep-2018 11:32:07 CEST Ekaitz Zárraga 👹

     in reply to

     • .:Ninjatrappeur:.

     @Ninjatrappeur Now, seriously... I'm mostly catching only the Inserts/deletes and the specific selects.
     The multiple selects not because I'm not good enough to make this happen in an acceptable way.