Hello all, EA does have the ability to add user-defined "tagged fields" to any type of object. Then the SQL generating MDG can be customized to use the added tagged fields. Not sure if this will do what you want, but it might be an approach. At least the fields could be used to document needed adjustments.
jeff > From: Jacek Becla <[EMAIL PROTECTED]> > Organization: Stanford Linear Accelerator Center > Reply-To: LSST Data Management <[email protected]> > Date: Wed, 08 Mar 2006 09:33:40 -0800 > To: LSST Data Management <[email protected]> > Subject: Re: [LSST-data] SQL coding standard > > Keywords: DataAccWG > >> I think the constraint names should be unique in whole DB, not just in >> table. MySQL is rather forgiving in this regard, but other engines (e.g. >> postgresql) are not. >> >> In light of my previous comment, I suggest we use, for primary keys: >> >> pk_<TableName>_<columnName> >> >> or >> >> pk_<TableName>_<columnName1>_<columnName2>_... > > > Ok. > > >> Is there a good mechanism in EA to capture the engine-specific mods? > > If there is, then we have not found it yet. That is why we are > thinking about keeping a clean version, not polluted with db-specific > things, and add these extra things specific to given database > during post-processing. > > Jacek > _______________________________________________ > LSST-data mailing list > [email protected] > http://www.lsstmail.org/mailman/listinfo/lsst-data > _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
