Importing DTO to Database and/or creating schema

[Meverhart]

More of a question than an issue but I assume that someone here might be able to guide me a bit.

I'm using Laravel and writing an application to parse and display a bunch of stats for a summoner. My issue is getting the information contained in the DTO created by LeagueWrap into my database. Is there an automated way of setting up a database schema (migration) or do I have to map it out my hand? For an average game there's a lot of data fields to map and while I guess I could do it by hand it seems like a lot of work.

Along those same lines, would it be easier to work with JSON data? If so, is there an easy way to convert the DTO generated by LeagueWrap to JSON?

Sorry, new-ish to PHP and Laravel.

[dnlbauer]

The answer very much depends on what database you are planning to use. MongoDB for example allowes to insert json as data structure so it's very easy to integrate. For sql like databases it is harder because you need to put more effort into normalization. Yes, you can access the raw json data from the dtos. I think the function is `->raw() ` Meverhart <notifications@github.com> schrieb am Mi., 8. Feb. 2017, 16:55:

…

More of a question than an issue but I assume that someone here might be able to guide me a bit. I'm using Laravel and writing an application to parse and display a bunch of stats for a summoner. My issue is getting the information contained in the DTO created by LeagueWrap into my database. Is there an automated way of setting up a database schema (migration) or do I have to map it out my hand? For an average game there's a lot of data fields to map and while I guess I could do it by hand it seems like a lot of work. Along those same lines, would it be easier to work with JSON data? If so, is there an easy way to convert the DTO generated by LeagueWrap to JSON? Sorry, new-ish to PHP and Laravel. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#15>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEeQ8u2AagIyYekdvAm0RdEtzFYN6ruUks5raeWLgaJpZM4L6_zQ> .

[Meverhart]

I'll be using MySQL.

[Meverhart]

Simplest problem: I'm not sure how to best store the data your wrapper provides in my database.

[m1so]

It all depends on what you want to store (and analyze), sometimes it isn't necessary to store the whole json response, but only parts of it. Laravel's Eloquent supports MySQL, Postgres, MSSQL and SQLite I believe, but there are packages that add additional driver support for example for MongoDB. If you have any more questions feel free to post on the Riot Dev forums or on the Discord channel.

[Meverhart]

These responses were not helpful in the least. For the sake of example let's say I make this call to the API:

$match = $api->match()->match(1399898747);

I want to store everything it returns in a MySQL database. How do I go about doing that? Do I need a pre-definded database schema based around the data that my API call will return or can I automate that process since any call for match information will essentually return the same type of data.

[dnlbauer]

This is out of scope of this platform. You don't have a problem with the api itself or its implementation. As already said you can receive the raw response as array (see above). Persisting that data in a database is nothing that api wrapper is able to do but can be implemented on top of it. This is a topic that has already been discussed on the dev board multiple times so you should find your answer there. It has nothing to do with this api wrapper. Meverhart <notifications@github.com> schrieb am Do., 9. Feb. 2017, 15:38:

…

These responses were not helpful in the least. For the sake of example let's say I make this call to the API: $match = $api->match()->match(1399898747); I want to store everything it returns in a MySQL database. How do I go about doing that? Do I need a pre-definded database schema based around the data that my API call will return or can I automate that process since any call for match information will essentually return the same type of data. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEeQ8v9hhKAWrUflCXRNuXTLISVNot8Nks5rayTOgaJpZM4L6_zQ> .