Are there any plans to support this? It seems like a good idea because then LLBL could be used to perform queries across disperate data stores.

Do you mean multiple databases per project?

Walaa wrote:

Do you mean multiple databases per project?

That's indeed supported already. THough multiple databases, as in 'oracle and sqlserver' isn't supported and won't be supported, as entities are tied to a schema, which is of course tied to a db. What we will offer in the near future is a converter and DDL script templates so you can start a project on sqlserver (for example) and convert it to oracle, and generate DDL for oracle as well.

Otis wrote:

Walaa wrote:

Do you mean multiple databases per project?

That's indeed supported already. THough multiple databases, as in 'oracle and sqlserver' isn't supported and won't be supported, as entities are tied to a schema, which is of course tied to a db. What we will offer in the near future is a converter and DDL script templates so you can start a project on sqlserver (for example) and convert it to oracle, and generate DDL for oracle as well.

Yes I was thinking of a scenario like a CSLA fetch where customer record comes from SQL Server, the orders collection is filled from Oracle, and the order shipping status is filled from a FedEx web service. It's a silly example, but you get the idea.

If LLBL can't do "views" across database systems, is how would you suggest building a composite business object like I described?

I guess it's better to have a DAL for each and every database you are working with, all are referenced by a Business Layer which manage the transactions between those databases.

You can use adapter to have a single set of entities and you then have as Walaa suggests, for every db a dbspecific project. You then can't do a recursive save or prefetch paths to fetch a hierarchy over multiple db's but you can do it per entity type if you want to.