I didn't know about the patters or intentions, but my gut feeling always has said that programmers make the yellow sun look like Earth's solar system (I realise that in truth the Earth is not on all yellow suns, and that the gut feeling is stupid at best).

I remember the Dread Lords spawned in my galaxy, and after I stopped their reign of terror I found out that their planet "Amalda" was a native class 60. After I took control of it, my planet quality abilities and PQ improvements made every single tile available. I was beside myself with joy; I seriously have never seen anything like it since, maybe it was a bug?

Then there was a time I found a planet with a PQ of 1, or a blue star with five "Purple water" habitable planets or that time my game glitched out and spawned a solitary planet without a star.

Hopefully the the planet-generation system in Galactic Civilizations 3 is more random and less deterministic than its predecessors; the outliers and the exceptions make the game more fun in my opinion. Things like rogue planets, binary stars, more varied planet environments and the like would really add a lot of personality to the game.

Here' hoping Stardock can make it happen

Maybe. Amalda has a base PQ of 36, if I'm not mistaken. Still, it's possible that one of the PQ enhancing random events happened.

Those are extremely rare in TotA, along with PQ 2 worlds. I'm not sure, if they are even supposed to appear in TotA anymore. In DA, on the other hand, they are much more common.

I am/was playing the current version of TA.

That being said, I've only ever seen one once, on an immense map with abundant everything. I found it by accident by going to the planet list and searching "planets- sort by class". I was so surprised.

With all my abilities, it became a class 26 :3

PQ1 planets? I have seen only one per game, and it was always named "Wisp". I never saw any PQ2s or PQ3s, but perhaps "Wisp" could be enhanced to those levels. And "Mars" in Sol's orbit has always started as PQ4. 

Hum. I'll have to look again when I have time.

What .NET will do automatically is release the managed memory when not referenced any more. But in truth you are probably not talking about that with the dbs issues. What you are talking about is disposing a object by doing something object specific. In case of dbs, it means sending something to the db engine and basically saying 'please close the connection'. That is not something .NET can do, unless of course  you'll tell how to do it by using IDisposable interface and the 'using' keyword. Normal Microsoft libraries regarding mssql have that interface, but it is still your job to use it. There could be also bugs, since those libraries use to some extent the unmanaged hell (another thing .NET cannot control).