You searched for the word(s): 40
In my project I have two models:
A. Retail Management
Model A has separate pages for concepts Customer, Item, Order, Sales, etc. It has no concept of Scheduling.
Model B is intended to extend Model A, introducing Scheduling concepts that refer to entities in Model A.
The same entity appearing on more than one ...
I didn't have my Wheaties. in place of \Visual Studio\ I meant \Visual Studio 2005
E:\Visual Studio\Projects\My_Project\ (as expected)
.cs files, including those generated from a .orm file end up in:
E:\Visual Studio\Projects\My_Project\My_Project\*.cs , My_Project.csproj
E:\Visual Studio ...
...from both my PC at the office AND at home.
I have my project saved on a USB pen drive so that I can work on it from both my PC at the office at home.
The pen drive is mapped at E: on both machines.
In Visual Studio > Options > Projects and Solutions, Visual Studio projects location: is set to
E:\Visual Studio 2005\Projects
Thus, my project is located in
E:\Visual Studio ...
Good to see that you found the source of your error, and that you are willing to own up to a simple mistake. Such mistakes are far from uncommon - for both people new to the subject, and for people that have worked with this stuff for some time. My guess is that you found the mistake the same way I often catch mine: you've thought it ...
Silly me. that was an external uniquness constraint set to preferred itentifier -- not an equality constraint. They do look very similar. All is clear to me now...
''... might be better that to use it as a DB schema requirement''
Where could I learn more about setting DB schema requirments?
I'm trying to follow the directions to recreate the diagram in Lab 4, slide 24
In the model notes there is a textual constraint:
For each Project: existing completionDate >= startDate
I believe startDate and completionDate are supposed to be role names. in the PPT, these are shown as bracketed blue text by the respective FactTypes. I ...
thanks Brian, your explanation regarding role sequences clarifies the matter. maybe one day the constraint should be re-named 'sequence constraint'
for anyone who might be interested in the exercise left to the reader on the last page of Lab 4,
I did the following tests.
Thing is a real thing
Thing is a tangible thing
The name 'equality constraint' may be misleading. You might think that it's some form of test for equality of values. What the constraint really enforces is a constraint on which roles, or role sequences must be played by an object, if that object participates in a role or role sequence in a different fact type. For example, if you had a ...