{"push_id":562566167,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"c39217c4b53add5c44dbab79ec54e107da713223","before":"4d307de3e0da6c45de68d90b4204c0693b362bee","commits":[{"sha":"28a0e54f76f112c0502631269b70d660f197cd30","author":{"email":"1ff4181aab696b798c77705446704f8379072f07@sasktel.net","name":"Mark Sobkow"},"message":"Add the SysCluster object, which is a singleton that will be\ninitialized/populated when setting the system password in the\nSecurity Manager web interface.","distinct":true,"url":"https://api.github.com/repos/msobkow/net-sourceforge-MSSCodeFactory-CFDbTest-2-2/commits/28a0e54f76f112c0502631269b70d660f197cd30"},{"sha":"c39217c4b53add5c44dbab79ec54e107da713223","author":{"email":"1ff4181aab696b798c77705446704f8379072f07@sasktel.net","name":"Mark Sobkow"},"message":"The SysCluster table is now the closest I can get to an enforced\nsingleton by specifying a non-generated primary key that is initialized\nto 1.  Unless someone goes to an artificial effort to do otherwise, this\nwill prevent multiple instances from being created in the database.  If\nI could be assured that only stored procedures were ever used to access\nthe database tables, I'd go to the effort of customizing the sp_create\nstored procs for the table, but I know that's not the case for most\ndatabases, so I won't bother.  Instead, I'll make sure that I check for\nmultiple entries in the Security Manager code during the initialization\nof the servlets.","distinct":true,"url":"https://api.github.com/repos/msobkow/net-sourceforge-MSSCodeFactory-CFDbTest-2-2/commits/c39217c4b53add5c44dbab79ec54e107da713223"}]}