Guides Update

Updated the guides and removed the use of application.wo prefix.
Updated the tests.yml file and enabled the adobe 2018 with sql server test suite.

Author: zainforbjs

.github/workflows/tests.yml

@@ -41,8 +41,8 @@ jobs:
           #   dbengine: mysql
           # - cfengine: adobe@2018
           #   dbengine: postgres
-          - cfengine: adobe@2018
-            dbengine: sqlserver_cicd
+          # - cfengine: adobe@2018
+          #   dbengine: sqlserver_cicd
           - cfengine: adobe@2018
             dbengine: h2
           # - cfengine: adobe@2021

guides/database-interaction-through-models/associations.md

@@ -76,7 +76,7 @@ For example, let's say that we only want to use `age` to return users who are in
 Example Code
 
 ```javascript
-users = application.wo.model("user").findAll(
+users = model("user").findAll(
         where="age >= 20 AND age < 30", order="age DESC"
 );
 ```
@@ -87,7 +87,7 @@ By default, calculated properties will return `char` as the column data type. Wh
 
 ```javascript
 property(
-  name="createdAtAlias", 
+  name="createdAtAlias",
   sql="posts.createdat", 
   dataType="datetime"
 );

guides/database-interaction-through-models/calculated-properties.md

@@ -17,13 +17,13 @@ Let's start with the [count()](https://api.cfwheels.org/model.count.html) functi
 To count how many rows you have in your `authors` table, simply do this:
 
 ```javascript
-authorCount = application.wo.model("author").count();
+authorCount = model("author").count();
 ```
 
 What if you only want to count authors with a last name starting with "A"? Like the [findAll()](https://api.cfwheels.org/model.findall.html) function, [count()](https://api.cfwheels.org/model.count.html) will accept a `where` argument, so you can do this:
 
 ```javascript
-authorCount = application.wo.model("author").count(where="lastName LIKE 'A%'");
+authorCount = model("author").count(where="lastName LIKE 'A%'");
 ```
 
 Simple enough. But what if you wanted to count only authors in the USA, and that information is stored in a different table? Let's say you have stored country information in a table called `profiles` and also setup a `hasOne` / `belongsTo` association between the `author` and `profile` models.
@@ -33,13 +33,13 @@ Just like in the [findAll()](https://api.cfwheels.org/model.findall.html) functi
 In our case, the code would end up looking something like this:
 
 ```javascript
-authorCount = application.wo.model("author").count(include="profile", where="countryId=1 AND lastName LIKE 'A%'");
+authorCount = model("author").count(include="profile", where="countryId=1 AND lastName LIKE 'A%'");
 ```
 
 Or, if you care more about readability than performance, why not just join in the `countries` table as well?
 
 ```javascript
-authorCount = application.wo.model("author").count(include="profile(country)", where="name='USA' AND lastName LIKE 'A%'");
+authorCount = model("author").count(include="profile(country)", where="name='USA' AND lastName LIKE 'A%'");
 ```
 
 In the background, these functions all perform SQL that looks like this:
@@ -57,7 +57,7 @@ However, if you include a `hasMany` association, CFWheels will be smart enough t
 For example, the following method call:
 
 ```javascript
-authorCount = application.wo.model("author").count(include="books", where="title LIKE 'Wheels%'");
+authorCount = model("author").count(include="books", where="title LIKE 'Wheels%'");
 ```
 
 Will execute this SQL (presuming `id` is the primary key of the `authors` table and the correct associations have been setup):
@@ -81,7 +81,7 @@ The same goes for the remaining column statistics functions as well; they all ac
 Here's an example of getting the average salary in a specific department:
 
 ```javascript
-avgSalary = application.wo.model("employee").average(property="salary", where="departmentId=1");
+avgSalary = model("employee").average(property="salary", where="departmentId=1");
 ```
 
 You can also pass in `distinct=true` to this function if you want to include only each unique instance of a value in the average calculation.
@@ -93,8 +93,8 @@ To get the highest and lowest values for a property, you can use the [minimum()]
 They are pretty self explanatory, as you can tell by the following examples:
 
 ```javascript
-highestSalary = application.wo.model("employee").maximum("salary");
-lowestSalary = application.wo.model("employee").minimum("salary");
+highestSalary = model("employee").maximum("salary");
+lowestSalary = model("employee").minimum("salary");
 ```
 
 ### Getting the Sum of All Values
@@ -106,15 +106,15 @@ As you have probably already figured out, [sum()](https://api.cfwheels.org/model
 Let's wrap up this chapter on a happy note by getting the total dollar amount you've made:
 
 ```javascript
-howRichAmI = application.wo.model("invoice").sum("billedAmount");
+howRichAmI = model("invoice").sum("billedAmount");
 ```
 
 ### Grouping Your Results
 
 All of the methods we've covered in this chapter accepts the `group` argument. Let's build on the example with getting the average salary for a department above, but this time, let's get the average for all departments instead.
 
 ```javascript
-avgSalaries = application.wo.model("employee").average(property="salary", group="departmentId");
+avgSalaries = model("employee").average(property="salary", group="departmentId");
 ```
 
 When you choose to group results like this you get a `cfquery` result set back, as opposed to a single value.

guides/database-interaction-through-models/column-statistics.md

@@ -7,7 +7,7 @@ description: How to create new objects and save them to the database.
 In Wheels, one way to create objects that represent records in our table is by calling the [new()](https://api.cfwheels.org/model.new.html) class-level method.
 
 ```javascript
-newAuthor = application.wo.model("author").new();
+newAuthor = model("author").new();
 ```
 
 We now have an empty `Author` object that we can start filling in properties for. These properties correspond with the columns in the `authors` database table, unless you have mapped them specifically to columns with other names (or mapped to an entirely different table).
@@ -30,7 +30,7 @@ If you want to create a new object based on parameters sent in from a form reque
 Given that `params.newAuthor` is a struct containing the `firstName` and `lastName` variables, the code below does the same as the code above (without saving it though).
 
 ```javascript
-newAuthor = application.wo.model("author").new(params.newAuthor);
+newAuthor = model("author").new(params.newAuthor);
 ```
 
 ### Saving Straight to the Database
@@ -39,7 +39,7 @@ If you want to save a new author to the database right away, you can use the [cr
 
 {% code title="" %}
 ```javascript
-application.wo.model("author").create(params.newAuthor);
+model("author").create(params.newAuthor);
 ```
 {% endcode %}
 
@@ -51,7 +51,7 @@ This means you can read the value by doing something like this. (This example as
 
 ```javascript
 <cfscript>
-newAuthor = application.wo.model("author").new();
+newAuthor = model("author").new();
 newAuthor.firstName = "Joe";
 newAuthor.lastName = "Jones";
 newAuthor.save();
@@ -72,7 +72,7 @@ However, unlike the primary key, Wheels will not automatically load database def
 Of course, if you do need to access the database default immediately after saving, Wheels allows this. Simply add `reload=true` to the [create()](https://api.cfwheels.org/model.create.html), [update()](https://api.cfwheels.org/model.update.html), or [save()](https://api.cfwheels.org/model.save.html) methods:
 
 ```javascript
-newAuthor = application.wo.model("author").new();
+newAuthor = model("author").new();
 newAuthor.firstName = "Joe";
 newAuthor.lastName = "Jones";
 newAuthor.save(reload=true);
@@ -89,7 +89,7 @@ property(name="welcomeText", defaultValue="Hello world!");
 This is effectively the same as doing this:
 
 ```javascript
-application.wo.model("myModel").new(welcomeText="Hello world!");
+model("myModel").new(welcomeText="Hello world!");
 ```
 
 ..except you only need to set it once per model.

guides/database-interaction-through-models/creating-records.md

@@ -23,7 +23,7 @@ If you're unfamiliar with the concept of callbacks, you can read about them in t
 Here's a simple example of fetching a record from the database and then deleting it.
 
 ```javascript
-aPost = application.wo.model("post").findByKey(33);
+aPost = model("post").findByKey(33);
 aPost.delete();
 ```
 

guides/database-interaction-through-models/deleting-records.md

@@ -25,7 +25,7 @@ Let's look at the methods Wheels provide to make tracking these changes easier f
 Let's get to coding…
 
 ```javascript
-post = application.wo.model("post").findByKey(1);
+post = model("post").findByKey(1);
 result = post.hasChanged();
 ```
 

guides/database-interaction-through-models/dirty-records.md

@@ -11,13 +11,13 @@ The concept is simple. Instead of using arguments to tell CFWheels what you want
 For example, the following code:
 
 ```javascript
-me = application.wo.model("user").findOne(where="email='me@myself.com'");
+me = model("user").findOne(where="email='me@myself.com'");
 ```
 
 Can also be written as:
 
 ```javascript
-me = application.wo.model("user").findOneByEmail("me@myself.com");
+me = model("user").findOneByEmail("me@myself.com");
 ```
 
 Through the power of `onMissingMethod()`, CFWheels will parse the method name and figure out that the value supplied is supposed to be matched against the `email` column.
@@ -27,7 +27,7 @@ Through the power of `onMissingMethod()`, CFWheels will parse the method name an
 You can take this one step further by using code such as:
 
 ```javascript
-me = application.wo.model("user").findOneByUserNameAndPassword("bob,pass");
+me = model("user").findOneByUserNameAndPassword("bob,pass");
 ```
 
 In this case, CFWheels will split the function name on the And part and determine that you want to find the record where the username column is "bob" and the password column is "pass".
@@ -45,13 +45,13 @@ In the background, these dynamically-named methods just pass along execution to
 The below code, for example, is perfectly valid:
 
 ```javascript
-users = application.wo.model("user").findAllByState(value="NY", order="name", page=3);
+users = model("user").findAllByState(value="NY", order="name", page=3);
 ```
 
 When passing in multiple arguments like above, you have to start naming them instead of relying on the order of the arguments though. When doing so, you need to name the argument `value` if you're passing in just one value and `values` if you're passing in multiple values in a list. In other words, you need to name it `values` when calling an `And`type dynamic finder.
 
 ```javascript
-users = application.wo.model("user").findAllByCityAndState(
+users = model("user").findAllByCityAndState(
         values="Buffalo,NY", order="name", page=3
 );
 ```

guides/database-interaction-through-models/dynamic-finders.md

@@ -22,7 +22,7 @@ This chapter will deal with the first part: getting the paginated data. Please p
 Let's jump straight to an example:
 
 ```javascript
-authors = application.wo.model("Author").findAll(page=2, perPage=25, order="lastName");
+authors = model("Author").findAll(page=2, perPage=25, order="lastName");
 ```
 
 That simple code will return authors 26-50 from the database, ordered by their last name.
@@ -32,7 +32,7 @@ What SQL statements are actually being executed depends on which database engine
 One important thing that you should be aware of is that pagination is done based on objects and not records. To illustrate what that means, we can expand on the above example a little:
 
 ```javascript
-authorsAndBooks = application.wo.model("Author").findAll(
+authorsAndBooks = model("Author").findAll(
   include="Books", page=2, perPage=25, order="lastName"
 );
 ```
@@ -42,7 +42,7 @@ Here, we tell Wheels that we also want to include any books written by the autho
 If you do want to paginate based on the books instead, all that you need to do is flip the `findAll()` statement around a little:
 
 ```javascript
-booksAndAuthors = application.wo.model("Book").findAll(
+booksAndAuthors = model("Book").findAll(
   include="Author", page=2, perPage=25, order="lastName"
 );
 ```

guides/database-interaction-through-models/getting-paginated-data.md

@@ -33,10 +33,10 @@ First, in our controller, let's set the data needed for our form:
 
 {% code title="app/controllers/User.cfc" %}
 ```javascript
-// In app/controllers/User.cfc 
+// In app/controllers/User.cfc
 function new() {
-    var newProfile = application.wo.model("profile").new();
-    user = application.wo.model("user").new(profile=newProfile);
+    var newProfile = model("profile").new();
+    user = model("user").new(profile=newProfile);
 }
 ```
 {% endcode %}
@@ -50,7 +50,7 @@ If this were an `edit` action calling an existing object, our call would need to
 {% code title="app/controllers/User.cfc" %}
 ```javascript
 function edit() {
-    user = application.wo.model("user").findByKey(key=params.key, include="profile");
+    user = model("user").findByKey(key=params.key, include="profile");
 }
 ```
 {% endcode %}
@@ -100,7 +100,7 @@ You may be surprised to find out that our standard `create` action does not chan
 {% code title="app/controllers/Users.cfc" %}
 ```javascript
 function create() {
-    user = application.wo.model("user").new(params.user);
+    user = model("user").new(params.user);
     if ( user.save() ) {
         flashInsert(success="The user was created successfully.");
         redirectTo(controller=params.controller);
@@ -123,7 +123,7 @@ For the `edit` scenario, this is what our `update` action would look like (which
 {% code title="app/controllers/Users.cfc" %}
 ```javascript
 function update() {
-    user = application.wo.model("user").findByKey(params.user.id);
+    user = model("user").findByKey(params.user.id);
     if ( user.update(params.user) ) {
         flashInsert(success="The user was updated successfully.");
         redirectTo(action="edit");
@@ -186,8 +186,8 @@ In this example, we'll just put one new `address` in the array.
 {% code title="app/controllers/Users.cfc" %}
 ```javascript
 function new() {
-    var newAddresses = [ application.wo.model("address").new() ];
-    user = application.wo.model("user").new(addresses=newAddresses);
+    var newAddresses = [ model("address").new() ];
+    user = model("user").new(addresses=newAddresses);
 }
 ```
 {% endcode %}
@@ -197,7 +197,7 @@ In the `edit` scenario, we just need to remember to call the `include` argument
 {% code title="app/controllers/Users.cfc" %}
 ```javascript
 function edit() {
-    user = application.wo.model("user").findByKey(key=params.key, include="addresses");
+    user = model("user").findByKey(key=params.key, include="addresses");
 }
 ```
 {% endcode %}
@@ -307,15 +307,15 @@ component extends="Model" {
     }
 
 }
-//  app/models/Publication.cfc 
+//  app/models/Publication.cfc
 component extends="Model" {
 
     public function config() {
         hasMany("subscriptions");
     }
 
 }
-//  app/models/Subscription.cfc 
+//  app/models/Subscription.cfc
 component extends="Model" {
 
     public function config() {
@@ -337,9 +337,9 @@ Here is how we would set up the nested properties in the `customer` model for th
 component extends="Model" {
 
     public function config() {
-        //  Associations 
+        //  Associations
         hasMany(name="subscriptions", shortcut="publications");
-        //  Nested properties 
+        //  Nested properties
         nestedProperties(
             associations="subscriptions",
             allowDelete=true
@@ -357,11 +357,11 @@ Let's define the data needed in an `edit` action in the controller at `app/contr
 {% code title="app/controllers/Customers.cfc" %}
 ```javascript
 function edit() {
-    customer = application.wo.model("customer").findByKey(
+    customer = model("customer").findByKey(
         key=params.key,
         include="subscriptions"
     );
-    publications = application.wo.model("publication").findAll(order="title");
+    publications = model("publication").findAll(order="title");
 }
 ```
 {% endcode %}
@@ -437,8 +437,8 @@ You'll notice that this example `update` action is fairly standard for a Wheels
 {% code title="app/controllers/Customers.cfc" %}
 ```javascript
 function update() {
-    //  Load customer object 
-    customer = application.wo.model("customer").findByKey(params.customer.id);
+    //  Load customer object
+    customer = model("customer").findByKey(params.customer.id);
     /*  If update is successful, generate success message
         and redirect back to edit screen */
     if ( customer.update(params.customer) ) {