Structuring PLSQL-Packages/Methods

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
asaake
Posts: 17
Joined: Tue 25 Mar 2008 16:51

Structuring PLSQL-Packages/Methods

Post by asaake » Thu 06 May 2010 14:58

We have lots of packages and functions/procedures in them.

If I import them via EntityDeveloper I have to manually add the package name to the method name. Otherwise I would get a problem with same proc names in different packages.

For a package function

vk_preis.preisfindung()

I get now a method

vk_preis_preisfindung(),

mixed into the many entities in my model.

It would be very helpful for me to get a tipp how to better structure this methods calls.

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Fri 07 May 2010 14:29

There is no way to change the name in design time without renaming every method.
We will investigate the possibility to deal with this scenario.
I can suggest you a workaround. Create a custom template and change the GenerateContextMethods method.
Add the following piece of code before the method name generation in the template:

Post Reply