Re: Structures_DataGrid addColumn() callback method change from 0.6.0
| From: | Andrew Nagy | Date: | Tue, 01 Feb 2005 17:42:15 +0000 |
| Subject: | Re: Structures_DataGrid addColumn() callback method change from 0.6.0 | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-17323@lists.php.net to get a copy of this message | ||
Jamie Alessio wrote:
For those people who don't define the columns, the '_' variables get printed. I think it is a good option to offer Thanks AndrewAndrew Nagy wrote:I just upgraded Structures_DataGrid from 0.6.0 to 0.6.2 and noticed that some of my scripts broke. In 0.6.0 the array passed to the callback function of the addColumn() method includes a slew of FormBuilder values, including '__table'. My code currently depends on this to create a generic function to add 'Edit/Delete' links to DataGrid tables.Well, I don't necessarily need it. The value was there so I was using it and was just surprised when it disappeared on me. What are the objections to having the extra data there? I searched the pear bugs db but didn't come up with anything that appeared to be related. - JamieOh I see, you do want the '__table' field? Hmm, I had many requests to drop this. Maybe it should be an option in the binding to either allow all variable or just the table fields. Could you add this as a feature request in the bug tracker?Are you using the latest version of DB_DataObject or atleast 1.7.0 or greater? The '__table' value is a dataobject value and should not be included in SDG as of DB_DataObject 1.7.0.I am using DB_DataObject 1.7.2 and the '__table' dataobject value is present in 0.6.0 of SDG, but not in 0.6.2 (both using DO 1.7.2). Now that I know the '__table' value isn't/shouldn't be in SDG I suppose I'll stop depending on it, but as far as I can tell there was a change in this from 0.6.0 to 0.6.2 that wasn't caused by DB_DataObject. Thanks for the response. - Jamie