Radicore Forum: How To » Failing searches, caused by null-able date fields

Home » RADICORE » How To » Failing searches, caused by null-able date fields

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: Failing searches, caused by null-able date fields [message #1368 is a reply to message #1367]

Tue, 10 June 2008 12:54

AJM
Messages: 2396
Registered: April 2006
Location: Surrey, UK

Senior Member

If a database table contains both a START_DATE and END_DATE field then when a search screen is initiated a field called CURR_OR_HIST is automatically added to the $fieldspec array, with the default value of 'C', to activate the feature described in http://www.tonymarston.net/php-mysql/infrastructure-faq.html #faq53. If you do not want this feature then you can remove this CURR_OR_HIST field from the data which is returned by the search screen using code in the _cm_changeConfig() method such as:

if ($GLOBALS['mode'] == 'search') {
    unset($this->fieldspec['curr_or_hist']);
} // if

Tony Marston
http://www.tonymarston.net
http://www.radicore.org

Report message to a moderator

[Message index]

		Failing searches, caused by null-able date fields By: ikatz on Tue, 10 June 2008 09:24
		Re: Failing searches, caused by null-able date fields By: AJM on Tue, 10 June 2008 12:54
		Re: Failing searches, caused by null-able date fields By: ikatz on Tue, 10 June 2008 14:37
		Re: Failing searches, caused by null-able date fields By: AJM on Tue, 10 June 2008 19:30

Previous Topic:	Use update2 pattern when I have two tables parent->child
Next Topic:	Screen structure reference for filepicker-ed images

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Sep 29 14:29:40 EDT 2026

Total time taken to generate the page: 0.01125 seconds