Re: bk commit into 5.1 tree (stewart:1.2030)

[Stewart Smith]

On Thu, 2005-09-29 at 16:40 -0400, SGreen@stripped wrote:
> I checked  Part 11 of the SQL2003 standard (ISO/IEC 9075-11:2003 (E))
> and didn't any INFORMATION_SCHEMA views for TABLESPACES or DATAFILES.
> Both seem to be rather implementation-specific sets of metadata. Does
> any other RDBMS product use the concept of a "tablespace"? If they
> did, do they expose that information through an INFORMATION_SCHEMA
> view? I couldn't think of any. 

Oracle has some views for tablespaces and the like.... although it's
specific enough to Oracle to probably not worry about. Anything we do is
going to be different enough anyway. Although we could use the same
column names for items that intersect.

I cannot for the life of me find out how to find unused space in MS SQL
Server (the MSDN docs don't want to say).

> So... as long as it looks good, and nobody can cite another reference
> I might have missed, you have just created the standard by which all
> other implementations will be judged :-) 

The next real trick is getting it consistent within mysql. I've coded
most of the stuff that's relevant for NDB. There is (doubtless) other
things that would be useful for InnoDB to export as well.

Also, is exporting information on MyISAM and the like sensible in a
table like this? You could view each MYD and MYI file as a tablespace
themselves.... although this data is available elsewhere.

suggestions welcome :)
-- 
Stewart Smith, Software Engineer
MySQL AB, www.mysql.com
Office: [phone] Ext: 6616
VoIP: 6616@stripped
Mobile: [phone]

Jumpstart your cluster:
http://www.mysql.com/consulting/packaged/cluster.html

Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc

Attachment: [application/pgp-signature]