Cosizzle's forum posts

#1 Posted by Cosizzle (6 posts) - - Show Bio

Maybe they're finally doing work on it... 
 
A boy can dream, eh

#2 Posted by Cosizzle (6 posts) - - Show Bio

Works for me, perhaps its your query?

#3 Posted by Cosizzle (6 posts) - - Show Bio

Hey, hopefully someone will be able to give me a little insight on this problem, but I'm kinda thinking it's something to do with the API itself which probably won't be addressed. Anyways Im running a search to get all the volumes of a specific name:  http://api.comicvine.com/search/?api_key=xxxxxx&resources=volume&query=batman&limit=20&offset=0&field_list=id,name,count_of_issues&format=json 
 
When the query return, the top 3 results are: 
 [0] => stdClass Object
    (
        [id] => 4720
        [count_of_issues] => 179
        [resource_type] => volume
        [name] => Batman: Legends of the Dark Knight
    ) 
[1] => stdClass Object
    (
        [id] => 4724
        [count_of_issues] => 96
        [resource_type] => volume
        [name] => Batman: Shadow Of The Bat
    )
[2] => stdClass Object
    (
        [id] => 3109
        [count_of_issues] => 27
        [resource_type] => volume
        [name] => Batman Annual
    )     
 
Is there a better way to get volumes by name? So that if in my case I search against batman, the first result would be batman.

#4 Posted by Cosizzle (6 posts) - - Show Bio

Yep, you can use the search call, so for example say I want to search Batman: 
 
       http://api.comicvine.com/search/?api_key=API_KEY&resources=volume&query=batman&limit=&offset=0&format=json 

#5 Edited by Cosizzle (6 posts) - - Show Bio

I'm sure he's killed Ra's a few times over... but that guys keeps coming back for more. 
 
Also: 
 

#6 Posted by Cosizzle (6 posts) - - Show Bio

I couldn't agree more with this post. 
 
Just this morning alone I wrote a 245 line class which runs a few queries, which isn't a lot I suppose. However what's upsetting is around 100 of those lines are going towards an ugly for loop which queries volumes, gets their ID's then goes and queries ALL the volumeIDs to get issue numbers. further more, I'm then having to sort the array afterwords so I can get the issue numbering in the correct order. Brute force works... but it really sucks and leads to some very messy code which leads to bugs and who knows what other headaches down the road. 
 
 /sign