Recent Changes

2020-03-28

• 18:40 UTC (new) 2020-03-28 psql as a PostgreSQL teacher . . . . Marcin Borkowski – A week ago, one of the commenters of my post from two weeks ago asked about the way to do stuff like \d (“describe table”) or \l (list the databases) etc. from SQL blocks in Org-mode. Well, the answer is – rather expectedly – “this is PostgreSQL, of course it’s possible”. Here’s how psql can teach you how to do it.

2020-03-23

• 22:14 UTC (diff) Comments on 2020-03-09 Using Org-mode as a PostgreSQL client . . . . Marcin Borkowski – Hi, thanks for all the comments! I'm very busy now, but I will address them in another post in a week or two -- stay tuned!
• 22:11 UTC (new) 2020-03-23 A rebase trick with disappearing commit . . . . Marcin Borkowski – Today, while working with Git, I discovered a very nice feature. I was working on a dedicated feature branch. Suddenly I discovered a bug which had to be fixed in order for that feature branch to make sense. However, the bug was not really connected with the feature I was working on. Well, it was connected in a sense, but it could affect other things as well, and I decided it should be fixed much earlier than I could possibly finish working on that feature – in other words, it deserved its own branch, based on the develop branch. So, I stashed my work, switched the current branch to develop, created a fixbug branch, fixed the bug, created a merge request and asked a colleague to review it. But here’s the deal: I could not work on my feature without that particular bug fixed. On the other hand, I wanted my feature branch to be based on develop and not on some other, random branch (well, that would work, but I like the history to be as clean as possible). What to do?
• 07:31 UTC (diff) Comments on 2020-03-09 Using Org-mode as a PostgreSQL client . . . . parisni – hi marcin. any substitute to \d (to describe table) or \l (to list databases) or \d+ (to describe views) and so on ? without those, you are stuck . . .

2020-03-16

• 20:28 UTC (new) 2020-03-16 COVID-19 . . . . Marcin Borkowski – It seems that everyone is talking about the COVID-19 pandemic now. Well, I decided to jump the bandwagon with a PSA. As all long-time readers of my blog know, it is a small tradition here to offer a decade of Rosary for all my readers on occasions of Easter and Christmas. I figure that a situation of life-endangering pandemic is a perfect opportunity to remember about prayer, so I am going to do the same also today.

2020-03-14

• 08:13 UTC (diff) Comments on 2020-03-09 Using Org-mode as a PostgreSQL client . . . . Anonymous – Hi simonfxr, For clarification, my comment was to Marcin in response to the original article, rather than in response to your own comment. I . . .

2020-03-11

• 22:37 UTC (diff) Comments on 2020-03-09 Using Org-mode as a PostgreSQL client . . . . simonfxr – I was mostly just commenting about heaving to put less information in the org source block headers. I know about linking sqli/sql buffers, but I . . .
• 02:39 UTC (diff) Comments on 2020-03-09 Using Org-mode as a PostgreSQL client . . . . Anonymous – > The canonical Emacs way is the Comint mode The canonical Emacs way to do what you're describing for SQL certainly *involves* the comint-based . . .
• 00:08 UTC (new) Comments on 2020-03-09 Using Org-mode as a PostgreSQL client . . . . simonfxr – Cool article! I've started using a similar setup recently. You can get away with a single header argument :dbconnection if you add all your settings . . .

2020-03-09

• 08:12 UTC (new) 2020-03-09 Using Org-mode as a PostgreSQL client . . . . Marcin Borkowski – I often have to write more or less complex SQL queries. In case of the easy ones, there is no problem – I just write them and that’s it. With more complex queries, however, it is very useful to adopt an incremental technique – writing them piece by piece. One of the best tools for such “incremental programming” is of course the REPL. In case of SQL (PostgreSQL in my case), this is usually solved with psql. While it has lots of nice features, editing a multiline query within it is not the nicest experience in the world. My first attempt to solving this problem was to use psql​‘s \e command. If given in the line on its own, it launches the default system editor with the previous query. While the readline library used by psql is fine, it is not very helpful in case of long, multiline queries – in such a case, a real editor like Emacs or Vim (or even a toy editor like everything else;-)) seems much better. After some time, however, I had an even better idea.

2020-03-02

• 21:10 UTC (new) 2020-03-02 PostgreSQL on Docker . . . . Marcin Borkowski – Lately, I’ve been experimenting with PostgreSQL a lot. It is of course convenient to be able to set up a temporary database to play around. I didn’t want to do it directly on my laptop. One solution was to use Virtualbox (with Vagrant). This is a nice way, and it is even apparently officially supported. (Go to the linked wiki page to learn about various possible reasons why you might want to run PostgreSQL in a VM.) However, I also wanted to try something different. I am completely new to Docker, and I figured that setting up PostgreSQL in Docker would be a good way to start introducing myself to this technology.

More...