The following warnings occurred:

Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.2.25 (Linux) File Line Function /global.php(961) : eval()'d code 26 errorHandler->error /global.php 961 eval /printthread.php 16 require_once

Make SQL Consistent With Code - Printable Version +- UserSpice (https://userspice.com/forums) +-- Forum: General (https://userspice.com/forums/forumdisplay.php?fid=20) +--- Forum: UserSpice 5 - Roadmapping the Future (https://userspice.com/forums/forumdisplay.php?fid=31) +--- Thread: Make SQL Consistent With Code (/showthread.php?tid=408)

Make SQL Consistent With Code - Trioxin - 12-27-2016 Currently, camel-case is being used in the code (Good) and underscores are being used for SQL (Not so good). Please change SQL names to use theSameCamelCase. I might refactor everything to be like this at the end of coding my current project but of course it would be better if future versions of userspice were consistent. Make SQL Consistent With Code - Trioxin - 01-21-2017 Oh, also filenames would be nice camel-cased as well. All should be consistent. Easy refactoring in an IDE. Make SQL Consistent With Code - plb - 01-22-2017 I don't agree re camel-casing for table- and column-names. Consistency is more important than going one way or the other. Userspice has been fairly consistent at using camel-case for PHP variables and underscores for column names. This probably comes from our (now somewhat distant) ancestor cakePHP - https://book.cakephp.org/3.0/en/intro/conventions.html#model-and-database-conventions. I would not want to change case for SQL entities.