CiviCRM Community Forums (archive)

Hey,

I have an extension with some generic stuff for my client. One of the things I usually do in this kind of extension is to create the custom fields, relationship types etc....

One of the things which should be created by this generic extensions are some smart groups. Now I can see from the Group API that I have the contents for the smart group and create them on enabling of my extension. However I see that the selectTables and the whereTables are returned as a serialized string which seems to be an array of string when you unserialize them. I would assume that in the return value of the API is not a serialized one but a JSON array.

Below an example of the returned Group from the API

{
"id":"2",
"name":"import",
"title":"import",
"description":"De contacten in deze groep komen van de oude CRM.",
"source":"",
"saved_search_id":"",
"is_active":"1",
"visibility":"User and User Admin Only",
"where_clause":" ( `civicrm_group_contact-2`.group_id IN ( 2 ) AND `civicrm_group_contact-2`.status IN (\"Added\") ) ",
"select_tables":"a:8:{s:15:\"civicrm_contact\";i:1;s:15:\"civicrm_address\";i:1;s:15:\"civicrm_country\";i:1;s:13:\"civicrm_email\";i:1;s:13:\"civicrm_phone\";i:1;s:10:\"civicrm_im\";i:1;s:19:\"civicrm_worldregion\";i:1;s:25:\"`civicrm_group_contact-2`\";s:165:\" LEFT JOIN civicrm_group_contact `civicrm_group_contact-2` ON ( contact_a.id = `civicrm_group_contact-2`.contact_id AND `civicrm_group_contact-2`.group_id IN ( 2 ) )\";}",
"where_tables":"a:2:{s:15:\"civicrm_contact\";i:1;s:25:\"`civicrm_group_contact-2`\";s:165:\" LEFT JOIN civicrm_group_contact `civicrm_group_contact-2` ON ( contact_a.id = `civicrm_group_contact-2`.contact_id AND `civicrm_group_contact-2`.group_id IN ( 2 ) )\";}",
"group_type":"",
"cache_date":"",
"refresh_date":"",
"parents":"",
"children":"",
"is_hidden":"0",
"is_reserved":"0",
"created_id":""
},


Ok. So what should be the standard here? The josn encode return (or xml) or the php serialized one?
I would argue the first one.

I can understand the API works like that from historic perspective, i am also happy to report this as an issue and provide a patch for it.

It makes sense to me that the api should unpack this to an array (which will wind up as an array to php users & json to Rest users). The DB storage mechanism would be uncoupled from the api format in a way that seems consistent with other places