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
/showthread.php 28 require_once





× This forum is read only. As of July 23, 2019, the UserSpice forums have been closed. To receive support, please join our Discord by clicking here. Thank you!
UserSpice   ›   General   ›   UserSpice 5 - Roadmapping the Future   ›   Make SQL Consistent With Code

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Make SQL Consistent With Code
plb
User
Joined: Aug 2016
Posts: 120

Reputation: 0
#3
01-22-2017, 09:38 AM
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/co...onventions.

I would not want to change case for SQL entities.
  Website
  Reply


Messages In This Thread
Make SQL Consistent With Code - by Trioxin - 12-27-2016, 12:09 AM
Make SQL Consistent With Code - by Trioxin - 01-21-2017, 09:14 AM
Make SQL Consistent With Code - by plb - 01-22-2017, 09:38 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)