This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello, i started today using LightSpeed express in order to evaluate it, in particular i need to use the linq to oracle feature and i am testing on two tables with a many-to-one relation when i drag the two tables into the new model, some fields are missing in the created classes, like a varchar(2) field named "Stato" or another varchar(2) named "Origine" is there any issue related to this problem? if i manually add the fields everything works fine, but its just odd to check all the fields to see if someone is missing thanks in advance Francesco |
|
|
|
|
Are those columns foreign keys? If so, we are inferring them as associations, which will appear once you drag the associated entity onto the diagram. (An association automatically includes a foreign key field, so we don't display the FK field on the designer surface.) Similarly, primary keys are mapped to the (implicit) Id property and do not appear on the designer surface. If the columns aren't primary or foreign keys, then it may be a bug, though it's not one we've seen before. In this case, could you provide us with the CREATE TABLE statements for these tables so we can try to reproduce and investigate this? Thanks! |
|
|
|
|
Looking into the table definition, i noticed that those fields are foreign keys on lookup tables, since the field "Stato", for example, contains only the letters "A" or "C" The solution is to manually add the missing fields, or just dragging the lookup tables should do the trick? Thanks for your reply Francesco |
|
|
|
|
Yep, if you want to be able to do the lookups, drag on the lookup tables, and LightSpeed should wire up the associations automatically. Note that in this case the LightSpeed FK property will be called something like StatoId because LightSpeed requires FK fields to be named XxxId, but it will still map it onto the Stato column in your database table. If you don't need to be able to do the lookups, then you can manually add the missing fields, though if you use designer-database synchronisation this may result in the designer wanting to delete them every time you do a sync (because it wants to map the columsn to associations so it thinks the fields are duplicates): you can work around this by clearing the relevant checkboxes in the "update" dialog. |
|
|
|
|
Thank you, i was looking for a strong product for "linq to oracle" and this one seems the best choice Keep the good work and thanks again for your quick replies Francesco |
|
|
|
