'Stored routines' Tag

  • Baffling 5.7 global/status variables issues, unclean migration path

    August 7, 2015

    MySQL 5.7 introduces a change in the way we query for global variables and status variables: the INFORMATION_SCHEMA.(GLOBAL|SESSION)_(VARIABLES|STATUS) tables are now deprecated and empty. Instead, we are to use the respective performance_schema.(global|session)_(variables|status) tables. But the change goes farther than that; there is also a security change. Oracle¬†created a¬†pitfall of 2 changes at the same time: […]

  • Why delegating code to MySQL Stored Routines is poor engineering practice

    February 6, 2014

    I happen to use stored routines with MySQL. In fact, my open source project common_schema heavily utilizes them. DBA-wise, I think they provide with a lot of power (alas, the ANSI:SQL 2003 syntax feels more like COBOL than a sane programming language, which is why I use QueryScript instead). However I wish to discuss the […]

  • common_schema & openark-kit in the media: #DBHangOps, OurSQL

    June 26, 2013

    #DBHangOps I had the pleasure of joining into @DBHangOps today, and speak about common_schema and openark-kit. What was meant to be a 15 minute session turned to be 50 -- sorry, people, I don't talk as much at home, but when it comes to my pet projects... I also realized I was missing on a […]

  • Taking common_schema's rdebug to a test-drive

    April 9, 2013

    This is a simple step-by-step introduction to rdebug: Debugger and Debugging API for MySQL Stored Routines, as part of common_schema. In other words: let me take you through the steps for debugging your stored routines on your own server. We will step into, step over, step out, modify variables, set a breakpoint, run to breakpoint... […]

  • common_schema 2.0.0-alpha: rdebug, GPL

    April 9, 2013

    A new release for common_schema: an alpha version of rdebug: MySQL Debugger and Debugging API is now included with common_schema. With a different license in mind for rdebug, common_schema changes license to GPL (2 or above). common_schema 2.0 is ready for download. All things rdebug, it is alpha -- otherwise it's a stable release. rdebug […]

  • MySQL Stored Routines Debugger & Debugging API: sneak preview II, video

    March 21, 2013

    This is the 2nd sneak preview of common_schema's rdebug: debugger & debugging API for MySQL stored routines (see 1st preview here). rdebug will be released as part of common_schema, free and open sourced. In this sneak preview I present: Compiling multiple routines with debug info Starting/stopping a debug session Step-over, step-in, step-out Showing stack trace […]

  • MySQL Stored Routines Debugger & Debugging API: sneak preview video

    February 19, 2013

    This is a sneak peek video introduction/preview of an in-development free and open source server side debugger & debugging API for MySQL stored routines. MySQL does not provide server side debugging capabilities for stored routines. Some tools exist, including MySQL's own, that assist in stored routine debugging. These are all GUI based and, to the […]

  • common_schema over traditional scripts

    December 12, 2012

    If you are familiar with both openark kit and common_schema, you'll notice I've incorporated some functionality already working in openark kit into common_schema, essentially rewriting what used to be a Python script into SQL/QueryScript. What was my reasoning for rewriting good code? I wish to explain that, and provide with a couple examples. I'm generally […]

  • Things that can't (and some that can) be done from within a MySQL stored routine

    August 2, 2012

    I'm doing a lot of stored routine programming lately, working on common_schema. I'm in particular touching at the extremes of abilities. Some things just can't be done from within a stored routine. Here's a list of can't be done: Cursor for SHOW statements: can't be done -- this is explicitly blocked from operating (it once […]

  • MySQL error handling on server side: a NO GO!

    July 18, 2012

    There is no reasonable way to catch and diagnose errors on server side. It is nearly impossible to know exactly what went wrong. To illustrate, consider the following query: INSERT INTO my_table (my_column) VALUES (300); What could go wrong with this query? We might hit a UNIQUE KEY violation Or a FOREIGN KEY violation my_column […]

Powered by Wordpress and MySQL. Theme by openark.org