Techniquices

Mintty, Cygwin and SuperPutty issue Mintty.exe: Process has exited, so the requested information is not available. From  https://github.com/jimradford/superputty/issues/528 (...) I also had this issue, but was able to do some troubleshooting this evening. The issue is caused by the current version of mintty.exe distributed with cygwin. In the new version, if mintty thinks that it wasn't started from a terminal, it will fork itself and then exit. Since superputty doesn't notice this, it tries to wait on the initial mintty process, which has already exited. Fortunately, there is a mintty config setting to disable this behavior. Just add "daemonize=false" to the .minttyrc file in your cygwin home dir.

From  http://stackoverflow.com/questions/38549/what-is-the-difference-between-inner-join-and-outer-join example   (not using your example tables :-) I have a car rental company. Table car id : integer primary key autoincrement licence_plate : varchar purchase_date : date Table customer id : integer primary key autoincrement name : varchar Table rental id : integer primary key autoincrement car_id : integer bike_id : integer customer_id : integer rental_date : date Simple right? I have 10 records for cars because I have 10 cars. I've been running this business for 10 years, so I've got 1000 customers. And I rent the cars about 20x per year per cars = 10 years x 10 cars x 20 = 2000 rentals. If I store everything in one big table I've got 10x1000x2000 = 20 million records. If I store it in 3 tables I've got 10+1000+2000 = 3010 records. That's 3 orders of magnitude, so that's why I use 3 tables. But because I use 3 tables  (to save