From: Andreas A. <a.a...@th...> - 2001-08-17 09:01:11
|
Hi, > If the entity carried what UI components it should use, there would be no > "extra" information needed. I see your point. > You can make some basic assertations about a field, i.e. "this is usually > going to be a textbox that's 20 chars long." if you don't > explicitly define that 'format' then the default is assumed and you can continue > about your business. Ok, that's nice. > I can see use in having separate "settings" for the database and the app. Jepp. I think this is neccessary. Another question. Can a entity span say parts of one or more tables? Something similar like a view in SQL? In the example the complete db entitys are mapped in the definition. And so querys are genearated for all fields. But that might me overhead. So I would like to define a entity that spans parts of tables. E.g. If I have a enty defined called "Subscriptions" that span the tables.fields: user.userId user.login smssubscriptions.userId smssubscritpions.serviceId emailsubscriptions.userId emailsubscriptions.serviceId but the tbl user has more fields I do not need to query for this entity. But for this one it's just fine. Andi |