Forum:  LLBLGen Pro Runtime Framework

Thread:  Copy entity source name from designer


jovball (User)   Posted on: 09-Jan-2018 21:15:32.
My primary database these days is a legacy mainframe DB2 beast. Table and column names tend to be both terse and obtuse. An example (and easier than most we have) would be a table named PART_EMPL_HIST. We use the designer to rename that as ParticipantEmploymentHistory and we do the same for columns. This works great for coding.

Sometimes we are looking to run an ad-hoc query in an tool such as IBM Data Studio (Yuck, but it's the best that IBM has.) For that, I need the "real" table name. It would be helpful to grab it from the designer but I can't find any way to do it.

I'd like to have some way to copy the real name from the Catalog Explorer, perhaps from the context menu. It would make me _really_ happy if I could generate SQL statements from that context menu, ala SSMS. Select would be enough but I'm sure I'd find a way use DML statements too.

daelmo (Support Team)   Posted on: 10-Jan-2018 07:01:05.
You ca know the table name in the catalog explorer, Right?. Also, in the Project menu, you can generate a CREATE script.

So, what you want is a way to generate (in a file or in memory) a create statement for that table. Is that correct?


Otis (LLBLGen Pro Team)   Posted on: 10-Jan-2018 10:27:49.
hmm also have you looked at linqpad to run queries against the generated code/entities for adhoc queries? that would solve the problem for you to obtain the real table name.
jovball (User)   Posted on: 10-Jan-2018 16:09:13.
I'm not looking for the table DDL. This is for ad-hoc query purposes so I'm looking for just the table name (right-click "Copy table name") or a full select script like SSMS does (right-click "Generate Select script to clipboard").

I know that the table name is in the catalog explorer. And it's easy to get to from the entity. Regular Smiley
It's tedious and error-prone for me to look at the name there and type it into another window. Especially with our "wonderful" table names like "TCASE_ACT_XTRCT1" and "TITLE_XVI_PYT_HST." Dissapointed

LinqPad wouldn't solve the issue that I need to use some non .NET tools with DB2. Sometimes this is IBM DataStudio and other times it is a TN3270 session (green screen).



Otis (LLBLGen Pro Team)   Posted on: 11-Jan-2018 18:26:47.
Regular Smiley That's indeed something that one might need. Going from entity to mapped table and do something with that is perhaps currently a bit cumbersome (lots of navigating) which should be easier and the results should be usable with e.g. the clipboard.

We'll think of something to make this easier, also the idea of generating SQL is something to think about, as well as going quick to the mapped target and do something with that, e.g. copy the name and perhaps other info as well.
jovball (User)   Posted on: 20-Sep-2018 23:37:36.
I know that you're wrapping up work on v5.5 now. Any chance of something like this making it into v5.6?

Otis (LLBLGen Pro Team)   Posted on: 21-Sep-2018 10:19:44.
jovball wrote:
I know that you're wrapping up work on v5.5 now. Any chance of something like this making it into v5.6?

Chances are high, it won't make it into 5.5 tho.
jovball (User)   Posted on: 26-Sep-2018 16:01:42.
I'm fine with that. I know I'm probably an edge case with this request.