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.

In DA they were pretty common, but I've never seen anything under 4 in TA. The best part of the PQ1 planets (and why they were cut) is that the AI would not colonize them until every other available planet had been claimed. They frequently terraformed up to level 16, even 19 - and the AI just let the player have them.

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

Hopefully such AI tweaks aren't needed in GalCiv III, and the AI can compete with said asymmetrical information.

Purple stars I remember having the best planets (class 26s) on occasion, but those were rare.

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. 

I think you're mistaken. Wisp is the secondary planet in the Altarian home-system, and it's a PQ3 world (always has been). 

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

Ive seen such happen when using c# to dispose of connections to dbs after reading large data sets into memory (10,000 + records per read) the dispose method does not clean up when you call it.  Could not tell if the issue was related to MSSQL, DB or Oracle as connections were to all three and the service I was running also needed to keep running checks periodically for activity.

At the time I also thought that c# should not have an issue with memory but more research on the way dispose actually works suggests otherwise. To manage the AI and all of the things going on in this game and to do so across threads will be no easy task in any language including c#.

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).