Ya I think there is. That err_message I think is coming from pg, or is that transparent right from PostgreSQL? Again, I haven't chased where it's used, so maybe it was just for development feedback. I thought that there would be something like a "returning id" type of feedback, which I know is PostgreSQL. In fact, I think I will be needing that soon, for inserts.
On Monday, February 10, 2020 at 5:54:30 PM UTC-5, Jeremy Evans wrote: > > On Monday, February 10, 2020 at 1:04:14 PM UTC-8, BeeRich33 wrote: >> >> Ah ok. >> >> I'm redoing some stuff, so it's not imperative I stick to anything. >> Essentially, leaving INSERT or DELETE commands without any capture of >> errors makes me lose sleep at night. With pg, it would have >> res.error_message which was returned so some kind of $SDOUT or some kind of >> feedback. >> > > Maybe there is a misunderstanding. With Sequel, if a database query > causes a database error, that is raised as a Ruby exception. So unless you > are rescuing the exception and purposely choosing to ignore it, you must > handle it or the program stops running and outputs a backtrace. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/0113f959-86c0-436a-a544-15f1cdd2bc44%40googlegroups.com.
