Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Designer> data elements to entity definitions window default selection
 

Pages: 1
Designer
data elements to entity definitions window default selection
Page:1/1 

  Print all messages in this thread  
Poster Message
sapul
User



Location:
Turkey
Joined on:
11-Jan-2019 15:10:43
Posted:
42 posts
# Posted on: 14-Jun-2019 10:05:55. Goto attachments  
Hi
In my db catalog, there are tens of ORACLE objects that should exists but also i will not genarate
entity. ( Materialized Views, ADMIN TABLES, TEMP TABLE)

These objects are listed "selected". Each time, It takes a lot of time to deselect them first and select the table that I just added to Database.

Alternate 1)
As in the old design, is there an option that "not mapped" group is listed with no selection.

Alternate 2)
do I have a chance to "ignore" objects that I will never do entity defition and send to another list?

Alternate 3)
Select NONE button for all items (both mapped and not mapped)
  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14531 posts
# Posted on: 14-Jun-2019 10:46:49.  
You can select all unmapped entity rows (select the first and use Shift+DownArrow Keys), then press on the "Toggle Checkboxes..." button.

  Top
sapul
User



Location:
Turkey
Joined on:
11-Jan-2019 15:10:43
Posted:
42 posts
# Posted on: 14-Jun-2019 10:58:01.  
Of course I can. However, since there are dozens of lines to deselect, doing this every time reduces productivity and makes the process vulnerable. I am looking for elegant and fast solution.
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37645 posts
# Posted on: 14-Jun-2019 14:41:10.  
If you don't have elements mapped on them, you can exclude them from the schema in the catalog explorer: select them all in one go (shift/ctrl-drag) then right click and select 'exclude from catalog'. This will remove them from the project. Next time you refresh the catalog, they're not pre-checked, so you can then just check the table you want to add.

Would that work? If not, please let us know why, so we can think of something else.

In v5.6 we've implemented a filtering / search in this UI as well to narrow down the list so you can easily select them in the UI, but other than that, the main design is based on: if you won't map an element onto a table, just remove it from the catalog in the project.



Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
sapul
User



Location:
Turkey
Joined on:
11-Jan-2019 15:10:43
Posted:
42 posts
# Posted on: 14-Jun-2019 15:38:21.  
Quote:
If you don't have elements mapped on them, you can exclude them from the schema in the catalog explorer: select them all in one go (shift/ctrl-drag) then right click and select 'exclude from catalog'. This will remove them from the project. Next time you refresh the catalog, they're not pre-checked, so you can then just check the table you want to add.


Once the catalog maintenance is done, the selection process will only be for newly added tables.

it is a very reasonable solution.

Thank you 👍
  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.