Hi;

I am considering buying/using LBLGen and have a couple of questions:

1) Can I create my code using Sql Server - but the code will then run on any supported database?

2) Can LBLGen create the database or do we need to use a tool like ErWin to create schema scripts that are then used to create the database structure?

3) Can I use this in a very lightweight manner. I don't want a product like Hibernate that is caching, pooling, etc. I want something where I will open a connection, start a transaction, perform a could of inserts and/or updates, commit/close, and I'm done. I remain responsible for lazy reads/write, what's dirty, etc.

??? - thanks - dave

Dave, I can answer a few of those for you.

1) Not sure on this one.

2) You need to create the database yourself. LLBLGen relies on reading the database definitions to create all the classes.

3) Yes - that is exactly how you use it.

I can tell you this product is very nice.

1) Can I create my code using Sql Server - but the code will then run on any supported database?

Yes this is possible, please check the following thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=5579

2) Can LBLGen create the database or do we need to use a tool like ErWin to create schema scripts that are then used to create the database structure?

LLBLGen Pro starts it's job upon an already created schema.

3) Can I use this in a very lightweight manner. I don't want a product like Hibernate that is caching, pooling, etc. I want something where I will open a connection, start a transaction, perform a could of inserts and/or updates, commit/close, and I'm done. I remain responsible for lazy reads/write, what's dirty, etc.

Yes you can, please check the LLBLGen Pro documentation "Concepts -> Template sets"

Walaa wrote:

1) Can I create my code using Sql Server - but the code will then run on any supported database?

Yes this is possible, please check the following thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=5579

With the addition that you need to create a project for the other db as well. THough you don't have to rewrite your code for the other db.