LLBLGEN Pro 4.2 + PostGreSql 7.4 (npgsql) + EnterpriseDB

Posts   
 
    
pfbwitz
User
Posts: 2
Joined: 24-Nov-2016
# Posted on: 24-Nov-2016 08:59:39   

Hi,

I'm currently busy with porting an Oracle-database to a Postgres-database. Our Oracle-databases often consists of many packages and stored procedures. In order to maintain the same structure in Postgres as we have in our Oracle-databases, we implement Postgres EnterpriseDB (Advanced server or whatchamaycallit)

LLBLGEN can only interpret the ported FUNCTIONS from our databases (as procedures in LLBLGEN), but the ported packages are invisible. (as they are EnterpriseDB-specific).

For a smaller webapplication, I was able to port the stored procedures to functions and map them as such in LLBLGEN, but for larger (older) projects that rely heavily on packages/stored-procedures it would be too much work to port the database in the same fashion.

Any advice available on accessing the EnterpriseDB-features in LLBLGEN will be much appreciated.

Kind regards,

Peter, on behalf of Q-ray

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 24-Nov-2016 14:03:41   

EnterpriseDB is a fork of postgresql so if there are things not in postgresql but in EnterpriseDB we sadly don't support these.

However, I think there's a solution possible which is easier. According to: https://www.postgresql.org/docs/current/static/plpgsql-porting.html

you should use schemas to group functions instead of packages. Postgresql supports multiple schemas per catalog, oracle just schemas. I think that can solve your problem.

Frans Bouma | Lead developer LLBLGen Pro
pfbwitz
User
Posts: 2
Joined: 24-Nov-2016
# Posted on: 24-Nov-2016 14:32:27   

Otis wrote:

EnterpriseDB is a fork of postgresql so if there are things not in postgresql but in EnterpriseDB we sadly don't support these.

However, I think there's a solution possible which is easier. According to: https://www.postgresql.org/docs/current/static/plpgsql-porting.html

you should use schemas to group functions instead of packages. Postgresql supports multiple schemas per catalog, oracle just schemas. I think that can solve your problem.

thank you for your reply. I will continue investigating. I will probably recommend letting go of Oracle-principles and properly porting the code so that LLBLGen will be able to work with it.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 25-Nov-2016 09:21:45   

With a 'schema per package' policy you can get very far I think simple_smile Good luck simple_smile

Frans Bouma | Lead developer LLBLGen Pro