![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Enhancement Requests and Suggestions » View Thread |
Messages 1 to 3 of 3 total |
![]() |
Thu, May 9 2013 11:48 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Any chance?
I'm about to start a total rewrite of my query generator and I thought it would be nice to be able to define which columns are available inside the database catalog. My alternative is a table in the database. Roy Lambert |
Fri, May 10 2013 4:45 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Roy,
<< I'm about to start a total rewrite of my query generator and I thought it would be nice to be able to define which columns are available inside the database catalog. >> Why not just store the column attributes in the attributes for the table ? You can store as much as you want there. Tim Young Elevate Software www.elevatesoft.com |
Sat, May 11 2013 9:11 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Tim
><< I'm about to start a total rewrite of my query generator and I thought it >would be nice to be able to define which columns are available inside the >database catalog. >> > >Why not just store the column attributes in the attributes for the table ? >You can store as much as you want there. That was one of my thoughts as was using the columns description field or creating a catalog of my own. Non of those is as elegant as having a field for the column. I'm on the penultimate stage of my TMS removal project which is rewriting my query generator. Currently I use collections for storing all the definition information which is stored in the dfm. It works well but since I'm doing a rewrite I'm thinking of alternatives. Roy |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |