Note that there are some explanatory texts on larger screens.

plurals
  1. USanaximander
    primarykey
    data
    text
    plurals
    1. COThat's odd... I'm not seeing the BaseEntity properties in the database.
      singulars
    2. COI appreciate that, and normally I'd agree, but I know that this is likely to be needed. I'm building to deploy to a server with MSSQL Server, but I have other people who also want versions and at least one of them won't have access to that. There's no single system common to all the places this is going to be deployed to. If I know I can just write a new data access layer implementation and switch out a handful of bindings to deploy to somewhere else, it'll save me a tone of work later. That, and I want to learn how to do it properly, and this is a good opportunity.
      singulars
    3. COIf these classes are being POSTed back to the server then it depends whether or not the server can tell which is which when they arrive. For example, I once built a page that could accept one of several model types, so when it POSTed I didn't know which it had been given. In these cases you need to find a way of handling each class appropriately. In your example, `Form1` and `Form2` would inherit from `BaseForm` which would have a `PropNameCollision` which may or may not be abstract, as needed. If there is a method somewhere that handles these forms then that might become `BaseForm.Process()`.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload