Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Okay, Feel like I spent my whole life through breeze documentation. Anyways, Finally solved the issue. To be honest, this wasn't a problem in breeze (but I wonder why it doesn't override the actual <code>nameOnServer</code> when I provide one). It's an error made by one of the developers in the early stage of the database implementation (probably 6 years ago). If the database adhered to Pascal Case naming convention, things would have worked perfectly fine.</p> <p>As a solution I wrote a custom naming convention which corrects the naming convention error when it has <code>ID</code> in the name and combines it with <code>camelCase</code> naming convention.</p> <pre><code>var createInconsistenIDConvention = function () { var serverPropertyNameToClient = function (serverPropertyName, prop) { if (prop &amp;&amp; prop.isDataProperty &amp;&amp; (prop.nameOnServer &amp;&amp; prop.nameOnServer === "ID")) { return "id"; } else { var firstSection = serverPropertyName.substr(0, 1).toLowerCase(); var idSection = ""; if (serverPropertyName.substr(1).indexOf("ID") != -1) { firstSection += serverPropertyName.substr(1, serverPropertyName.substr(1).indexOf("ID")).toLowerCase() + "Id"; } else { firstSection += serverPropertyName.substr(1); } return firstSection; } } var clientPropertyNameToServer = function (clientPropertyName, prop) { if (prop &amp;&amp; prop.isDataProperty &amp;&amp; (prop.nameOnServer &amp;&amp; prop.nameOnServer.indexOf("ID") != -1)) { return prop.nameOnServer; } else { return clientPropertyName.substr(0, 1).toUpperCase() + clientPropertyName.substr(1); } } return new breeze.NamingConvention({ name: "inconsistenID", serverPropertyNameToClient: serverPropertyNameToClient, clientPropertyNameToServer: clientPropertyNameToServer }); }; </code></pre> <p>Not sure if the way I've used nameOnServer property is not correct. I couldn't find any documentation on that in breeze website.</p> <p>please note that the above code only consider situations like ID, CountryID, GameID, PersonID etc.</p> <p>Problem solved for now.</p>
    singulars
    1. This table or related slice is empty.
    1. PObreezejs addEntityType issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAmila
    1. USAmila
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PObreezejs addEntityType issue
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAmila,thanks for the comments. We DO need to do a better job documenting the metadata. i.e. nameOnServer vs name and the associated rules. Trying to get some of this documentation onto the website within the next few days, but we will still have a lot more to add. :)
      singulars
      1. PO
      1. USJay Traband
    2. COHi Jay. If one follows the tutorials, it helps somewhat to understand things and also, if when I get an error I debug it in the chrome console for hours. Doing so helped me to understand most of the stuff. Infact, I'm not using the above naming convention coz I figured out it'll be easy to change it in the edmx file in the long run. Now I'm trying to figure out how to assign lookups (list of countries) to a dropdown which is generated dynamically when the user clicks on edit. It's rather a knockout problem than a breezejs I think.
      singulars
      1. PO
      1. USAmila
    3. COThank you for this solution. It was driving me crazy that it was ignoring the nameOnServer property. I just wanted everything, client & server, to be camelCase!
      singulars
      1. PO
      1. USjdobry
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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