I hope you take something away...

If you do please leave something for me :)

Passing data within your controllers

/**
 * Created by nmeegama on 8/27/16.
 */
/************ Controller to set the data *******************/
(function (angular) {

    'use strict';
    angular.module('MyApp').controller('SetDataCtrl', [
        '$scope', 'MyService',
        function ($scope, MyService) {

            $scope.setData = function (data) {
                MyService.setData(data);
            };

        }]);
})(angular);

/************ Controller to get the data *******************/
(function (angular) {

    'use strict';
    angular.module('MyApp').controller('GetDataCtrl', [
        '$scope', 

Finding the JAVA_HOME in your Mac

Generally if you are not sure where your JAVA_HOME is the first thing you would do is type in the following command

echo $JAVA_HOME

But more times than usual if you have not intentionally set this variable in your MAC you would see an empty response. So now how would you proceed to find the real JAVA_HOME.  Some times a quick solution is looking in /System/Library/Frameworks/JavaVM.framework/Versions. Still there can be a lot of Java HOME's in there (like what happened to me).

REST mode in Drupal 8

Submitted by nmeegama on Mon, 06/20/2016 - 10:32

As you might already know Drupal 8 contains a web services layer out of the box. Therefore we can now easily create a RESTful Architecture by exposing Drupal's data to a third party application. REST stands for Representational State Transfer. It is a set of design principles for making network communication more scalable and flexible.

Setting up debug mode on Drupal 8

  1. First copy sites/example.settings.local.php to default/settings.local.php
  2. Now uncomment the following lines in default/settings.php
    # if (file_exists(__DIR__ . '/settings.local.php')) {
    #   include __DIR__ . '/settings.local.php';
    # }
  3. Now debugging is set. You also can use the following command
    drupal routing:debug <route name>
    This command will give the user information regarding a specific route

     

PostgreSQL and NOT IN

PostgreSQL treats LEFT JOIN and NOT EXISTS equally, using same execution plan for both of them (namely a Hash Anti Join for the example above).

As for NOT IN, which is semantically different since its logic is trivalent and it can return NULL, PostgreSQL tries to take this into account and limits itself to using a filter against a subplan (a hashed subplan for a hashable resultset like in example above).