MyMetaPluginContext : IMyMetaPluginContext

[Paqrat]

I downloaded the MyMetaPluginContext implementation of the IMyMetaPluginContext interface. That helps in knowing what to populate in the plugin.

Both MyMeta.ITable and MyMeta.IColumn have an Alias property. The Tables and Columns DataTables do not include a column for Alias. Can I add a column in both DataTables for Alias in MyMetaPluginContext so I can make that value available to MyMeta? Can I add other missing properties as new columns in the DataTables? Can I eliminate those columns in the DataTables that I will not be using?

The column names in the DataTables do not always correspond to the MyMeta property names. For example \"TABLE_GUID\" is not the same as \"ITable.Guid\" whereas \"DESCRIPTION\" does correspond to \"ITable.Description\". How does MyGeneration know that the value in \"TABLE_GUID\" corresponds to \"ITable.Guid\"?

[mike.griffin]

I started adding documentation and will try to finish it soon, see if this helps

http://www.mygenerationsoftware.com/por ... fault.aspx

[Paqrat]

Thanks, Mike. I actually started on that link. When it is completed, it will be very useful, but it does not address the question of MyMeta properties that are not shown. I really need to be able to use the MyMeta.Alias property, but the DataTable definitions for tables and columns do not include a column for it. Would it be as simple as adding a column or is it just not supported? If I can add the \"Alias\" column to the DataTables, what name would I use for the column? In looking at the column names in the MyMetaPluginContext implementation, there does not appear to be a consistant mapping between MyMeta property names and the DataTable column names.

[mike.griffin]

You're right about the mapping, the DataTables are driving by the OLEDB Schema Rowset information which most databases support and I use that to pull the Metadata, however, I gave the information nice names of course in MyMeta. I will double check the Alias, I am pretty sure it's there, if not I will add it, it just might be missing from the docs?