User tests: Successful: Unsuccessful:
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_contact Front End SQL Installation Postgresql |
Labels |
Added:
?
|
Category | Administration com_contact Front End SQL Installation Postgresql | ⇒ | SQL Administration com_admin com_contact Front End Installation Postgresql |
Title |
|
yes, to me too, we need to take a decision and make it consistently across the cms
I have tested this item
with MySQL and PostgreSQL.
Unless anyone feels strongly I'd rather have this set all the time. So modified date is always set (to the created date time when the article is created)
ok modified
field is not null
now
p.s.
i hope prepared statement should be room for a new pr
There's no queries here that require prepared statements. This looks fine. Just needs some tests creating and updating contacts
are you sure ?
just for example components/com_contact/Model/CategoryModel.php is full of places where we can use prepared statements
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
RTC
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-05-16 16:08:29 |
Closed_By | ⇒ | wilsonge | |
Labels |
Added:
?
|
Thanks!
Open question (can see it both ways). Should modified date by nullable or should enforce it being date time (modified date is the created date on creation).