I can make arguments both for and against this. There has been a number of times when I thought the use of an SQL backend would be 'nice', but doing it in Hash tables has been sufficient.
That being said, if it was included, perhaps the mindset that was used for SSL could be used: mIRC has the hooks, and should the appropriate libraries be available, the identifiers become available.
It would keep the bloat down a bit and not overload those users who don't need SQL.
Perhaps as a portability option, instead of tying ONE sql engine in, an ODBC or similar handle could be used, thus allowing the use of any external data source..
But, just throwing ideas around..
In all seriousness however, when you're starting to need this level of data storage and manipulation, it's beyond the point where you've exceeded the designs of the scripting language and engine anyway.
