Hi,

My application needs to change an Oracle schema at runtime, meaning creation of new tables, adding foreign keys etc. Of course, I would like to have LLBLGen create for me matching entities at runtime, but this is not that important....

Anyhow, does LLBLGen support DDL?

No, it doesn't support DDL as in: create new tables and automagically new .NET types are created for you .

I don't really need .NET types. I could think that having the class EntityBase2 means that I can put data into it and call a method that only creates a table in the database based on this type.

Is it possible? Or is there something else? I want to avoid SQL statements ("CREATE TABLE....."), much like when performing DML commands

No that's not possible, LLBLGen Pro doesn't support creation of schema elements like tables. So you have to use DDL statements.

OK, so here's my problem. My application - a web-services application - uses a single DB-connection for each web-service through its lifetime.

Having a simple set of DML commands my code will be something like:

mDataAccessAdapter.OpenConnection(); mDataAccessAdapter.FetchEntity(...); mDataAccessAdapter.SaveEntity(...); . . mDataAccessAdapter.CloseConnection();

But when I need to create a new table among the DML commands, I understand that I should use either ODP directly (and open a new connection) or DataAccessAdapter.ExecuteActionQuery() (and create a new connection).

1. Is it true that in the ExecuteActionQuery case I wouldn't have to open the connection? What do the DataAccessAdapter perform behind the scene?

2. Why, anyhow, do I have to create a new connection object? Why can't the DataAccessAdapter's connection be used in some way?

orenpeled wrote:

OK, so here's my problem. My application - a web-services application - uses a single DB-connection for each web-service through its lifetime.

Having a simple set of DML commands my code will be something like:

mDataAccessAdapter.OpenConnection(); mDataAccessAdapter.FetchEntity(...); mDataAccessAdapter.SaveEntity(...); . . mDataAccessAdapter.CloseConnection();

But when I need to create a new table among the DML commands, I understand that I should use either ODP directly (and open a new connection) or DataAccessAdapter.ExecuteActionQuery() (and create a new connection).

1. Is it true that in the ExecuteActionQuery case I wouldn't have to open the connection? What do the DataAccessAdapter perform behind the scene?

Thats done behind the scenes, yes

1. Why, anyhow, do I have to create a new connection object? Why can't the DataAccessAdapter's connection be used in some way?

You don't need to create your own connection, you can order the DataAccessAdapter to create one for you.