While developing mysql-proxy I sometimes have to step-by-step refactoring that usually result in unstable code for a while until the unit-tests are happy again. When a unit-test fails I usually use gdb as a wrapper and let it create a stack-trace for me: $ gdb --command=backtrace.gdb --args /path/to/my/testcase The --command option is used to automate gdb: run thread apply all bt quit If the test
Over the last weeks I wrote a mysql-proxy which changes the way you operate with the MySQL Server. A proxy can operate as Man in the Middle and pass through to network packets to the MySQL Server, but it also change the packets when needed. This opens the several possibilities like a pseudo server done injection proxy done load-balancing proxy done connection pool XA Transaction Manager replicatio
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く