Jane you ignorant slut. So in reality you have code to generate your first insert + catch new key value. More code to setup next insert(s) using that first Pkey value.
This is Four trips to the db for only single inserts to two tables and then update the master last_id data as well. Now add two more trips for each and every trip for each additional detail rows needed to be added. Bwahahahaha On Thu, Mar 24, 2016 at 3:17 PM, < [email protected]> wrote: > On 2016-03-24 14:17, Stephen Russell wrote: > >> You control freak. Let the backend do what it does so well. >> >> https://mariadb.com/kb/en/mariadb/auto_increment-faq/ >> >> I gave up on that single table of last PKs 15 + years ago when I found >> that >> the backend already did it for us, all we had to was ask for it. >> > > > From SNL: "Jane, you ignorant slut." lol > > Steve -- you might recall the original post from this thread that laid out > that there were multiple levels (3+) that were needing keys at record > creation time, so the AUTOINC on the backend was not an option as we were > creating datasets locally and then if the user saved, we committed to the > database. So your "let the backend do it" doesn't apply here. > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMYJuCqgYa10QCx34eNWx=_lpio4x3vbvyccy7x7nctt...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
