phpMyEdit - Viewing Bug Advanced Details			[ Go Back ]
ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
286	core / field option	feature	N/A	2004-11-28 23:32	2004-12-28 08:55
Reporter:	hbernard	Platform:	PC
Assigned To:	nepto	OS:	(Server) Linux Mandrake 9.1
Priority:	normal	Version:	Builtin
Status:	feedback	Product Version:
Product Build:		Resolution:	open
Projection:	none	Duplicate ID:
ETA:	none
Summary:	Making option variability one level deeper
Description:	Currently, option variability feature ('*|LF' => ) is available only at the first level of the field definition. It would be nice if we could implement one additionnal level.
Steps To Reproduce:
Additional Information / Solution:	Just to keep track of the (michal) idea.
System Description:
Attached Files:

Bug Notes
nepto    2004-11-28 23:40	I guess there is some note in the source concerning to this ;-) Something marked as "TODO" or so... I will take care of this. edited on: 2004-11-28 23:42
nepto    2004-11-29 00:32	Now I made up my mind I'm not sure about this... This could make several problems in ['values'] or better in ['values2']. For example someone would like to store pipe character "|" into database, so he or she would use: ['values2'] => array( 'barfoo|1' => 'Bar Foo', 'barfoo|2' => 'Another Bar Foo', ... ) Hm?
michal    2004-11-29 11:22	so he/she would have to use 'barfoo\|1' (escaping special character) (i hope that's possible to implement)
hbernard    2004-11-29 14:41	What about just exclude 'values2' from the scan ?
nepto    2004-12-28 01:24	The question is, if 'values2' is the only option which has to be excluded during scan...
hbernard    2004-12-28 08:55	Yes, I think values2 is the only case where the _keys_ of a sub-array are _user-defined_. Others keys are API-defined, or implicit integers (like in values). Correct me if I am wrong