Hi Mallah,
doc patches welcome! I know they are lacking.
Best regards, Alex
On 2017-03-01 07:43, Rajesh Kumar Mallah wrote:
Dear Dimitar/List ,
indeed the example 1 below was correct.
The confusion resulted form multiple mistakes in my
observations and actions.
Sorry for the noise. Now
Dear Dimitar/List ,
indeed the example 1 below was correct.
The confusion resulted form multiple mistakes in my
observations and actions.
Sorry for the noise. Now my primary concern is sorted out.
Regds
mallah.
> There are a couple of ways around that.
>
> 1. Search for that record id,
Now Looking into the test scripts that came with the distribution.
Hope to find the solution.
>
> Firstly thanks for the quick reply,
>
>
> http://10.100.102.38:3000/api/rest/general/members/368
> does respond with single record.
>
> {
> "data": {
> "group_id": null,
> "pan1": null,
Firstly thanks for the quick reply,
http://10.100.102.38:3000/api/rest/general/members/368
does respond with single record.
{
"data": {
"group_id": null,
"pan1": null,
"mobile2": null,
"pan2": null,
"pa_city": null,
"email": null,
"membership_no": null,
There are a couple of ways around that.
1. Search for that record id, for example:
http://10.100.102.38:3000/api/rest/general/members?limit=3_returns=holder1_returns=member_id_id=368
2. If it's a primary key or a unique key, you can easily fetch it:
I am trying to use Catalyst::Controller::DBIC::API::REST
to feed jtable with JSON
Eg :
the request
http://10.100.102.38:3000/api/rest/general/members?limit=3_returns=holder1_returns=member_id
Leads to response:
{
"Records": [
{
"member_id": 366,
"holder1": "Jinesh"
