Usually something like SP_0001, SP_0002 (for Stored Procedure), TG_0001, TG_0002 (for Trigger), TB0001, TB0002 (for Table), and so on. I am used to creating short names for objects. To support such structures with Firebird either requires simulating schema with quoted identifier names that have periods in them or a series of stored procedures that query cross database.Īlso, for queries, if you have a long identifier, used as embedded documentation, you use aliases in the query itself as in select a.* from myreallylongtablenamethatexplainsitsownpurpose a so the queries are not really impacted and if used properly are easier to debug.Īt this point, having a size of identifier that matches or exceeds the primary competition to ease porting, is the highest priority, but, in truth, we need proper recursive schema namespaces. With Oracle or DB2 you can often see recursive schema and the use of synonyms to separate out various name/query spaces with default schema as part of the fundamental part of the design. Then they would perform cross company queries for consolidated reports. For example, some accounting databases, use the same table structure/names but use different schema names to differentiate between companies such as company1.GeneralLedger etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |