Go has a debugger—and it's awesome!
Something that often, uh... bugs[1] Go developers is the lack of a proper debugger. Sure, builds are ridiculously fast and easy, and println(hex.Dump(b)) is your friend, but sometimes it would be nice to just set a breakpoint and step through that endless if chain or print a bunch of values without recompiling ten times. CC BY 2.0 image by Carl Milner You could try to use some dirty gdb hacks that
SQLã«ã‚ˆã‚‹ãƒ€ãƒ³ãƒ—
24.1. SQLã«ã‚ˆã‚‹ãƒ€ãƒ³ãƒ—ã“ã®ãƒ€ãƒ³ãƒ—方法ã®èƒŒæ™¯ã«ã‚る考ãˆæ–¹ã¯SQLコマンドã§ãƒ†ã‚ストファイルを生æˆã—ã€ãã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’サーãƒãŒå†åº¦èªã¿è¾¼ã¿ã‚’è¡Œã£ãŸæ™‚ã«ã€ãƒ€ãƒ³ãƒ—ã—ãŸæ™‚点ã¨åŒã˜çŠ¶æ…‹ãŒå†æ§‹ç¯‰ã•ã‚Œã‚‹ã¨ã„ã†ã“ã¨ã§ã™ã€‚ ã“ã®ç›®çš„ã®ãŸã‚ã€PostgreSQLã¯pg_dumpユーティリティプãƒã‚°ãƒ©ãƒ ã‚’æä¾›ã—ã¦ã„ã¾ã™ã€‚ ã“ã®ã‚³ãƒžãƒ³ãƒ‰ã®åŸºæœ¬ã¨ãªã‚‹ä½¿ã„æ–¹ã¯ä»¥ä¸‹ã®é€šã‚Šã§ã™ã€‚ pg_dump dbname > outfile 見ã¦ã‚ã‹ã‚‹é€šã‚Šã€pg_dumpã¯çµæžœã‚’標準出力ã«æ›¸ã出ã—ã¾ã™ã€‚ ã“ã‚ŒãŒã©ã®ã‚ˆã†ã«æ´»ç”¨ã§ãã‚‹ã‹ã‚’ã“ã‚Œã‹ã‚‰èª¬æ˜Žã—ã¾ã™ã€‚ pg_dumpã¯ã€ï¼ˆå„ªã‚ŒãŸæ©Ÿèƒ½ã‚’特ã«ç™ºæ®ã™ã‚‹ï¼‰PostgreSQLã®é€šå¸¸ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚¢ãƒ—リケーションã§ã™ã€‚ã¨ã„ã†ã“ã¨ã¯ã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã«æŽ¥ç¶šå¯èƒ½ãªã‚らゆるリモートホストã‹ã‚‰ã“ã®ãƒãƒƒã‚¯ã‚¢ãƒƒãƒ—æ‰‹é †ã‚’å®Ÿè¡Œã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã—ã‹ã—ã€pg_dumpã¯å‹•ä½œã«ç‰¹åˆ¥ãªæ¨©é™ã‚’å¿…è¦ã¨ã™ã‚‹ã‚ã‘ã§ã¯
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}