|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Ramov Tinoga
Tinoga Enterprises
|
Posted - 2008.12.23 11:43:00 -
[1]
Edited by: Ramov Tinoga on 23/12/2008 11:43:20
Originally by: Dragonaire
- Moved the function getAPIinfo() used to get data from API into it's own file inc/common_api.inc instead of having it in the inc/common_db.inc file.
revision 355 is up with the new changes enjoy.
Could you please submit the new inc/common_api.inc so we can use it too?
Thank you very much for Yapeal. I look forward to do crazy stuff with it. -----
|
Ramov Tinoga
Tinoga Enterprises
|
Posted - 2009.01.11 00:00:00 -
[2]
Originally by: Ragga daPhunk the only thing that gets updated in the database is the "CachedUntil" table but nothing else.
When I run the script manually once a day, everything is updated quite fine.
When its run by cron every five minutes (*/5), I noticed that only the CachedUntil table is updated, but none of the other tables. My server is running at GMT+1, so the times in the table and the local time are at different time zones. Could this cause the problem? |
Ramov Tinoga
Tinoga Enterprises
|
Posted - 2009.02.23 11:48:00 -
[3]
Dragionaire, thank you very much for the new framework!
To give you a heads up: I'm working on the implementation for the Standings API (character and corp).
I haven't seen an API that has a structure similar to the Char Standings API (two groups with several rowsets). From my first analysis and following the approach used in CorporationSheet, it would need 5 new tables for char and corp each.
- [char|corp]StandingsToCharacters
- [char|corp]StandingsToCorporations
- [char|corp]StandingsToAlliances
- [char|corp]StandingsFromAgent
- [char|corp]StandingsFromNPCCorporations
- [char|corp]StandingsFromFactions
But I think I'll merge them together so that a total of 4 tables (charStandingsTo, charStandingsFrom, corpStandingsTo, corpStandingsTo) with 5 fields (one of them an enum field for the rowset name) will do.
What do you think?
-----
|
Ramov Tinoga
Tinoga Enterprises
|
Posted - 2009.02.24 08:31:00 -
[4]
Originally by: Dragonaire Ok after looking at the both APIs some more the way I'd do the character one is to have the 5 tables named charStandingsToCharacters, charStandingsToCorporations, ..., [..]
Doing it this way does result in a large number of small tables with long table names but will make getting data back out in applications easier I believe.
When you're ok with 12 more tables, then I'm ok too. It's much easier to maintain in the code when there's just a multiupsert for each rowset without having to tackle the different cases. I had second thoughts because each half of the 12 tables has identical structure (fromID, fromName, standings / toID, toName, standings).
Quote: You've managed I believe to have picked one of the harder APIs to tackle first :)
Now that you mention it.. It's the one I'm missing most at the moment, so I started with that, "charStandingsFromNPCCorporations" to be particular.
-----
|
Ramov Tinoga
Tinoga Enterprises
|
Posted - 2010.01.06 11:15:00 -
[5]
Originally by: Dragonaire New version of the 'Alpha' installer out which should have fixed the errors with Map section and the problem with auto-detecting PHP under Linux. 'Legacy' should work correctly now as well as 'Advanced'.
revision 955
I've installed the Yapeal-955-linux-x64-installer.bin (Advanced Setup) on my openSUSE 11.0_x64 and it worked fine once I gave the yapeal database user all rights on the yapeal database.
I was a bit reluctant to update my old yapeal version manually, so the installer is really helpful and takes care of everything. -----
|
Ramov Tinoga
Tinoga Enterprises
|
Posted - 2011.03.15 13:05:00 -
[6]
Do your utilRegistered* tables contain entries with the activeAPI column being non-empty and isActive = 1?
Without that, yapeal will only fetch non-character related data from the API. -----
|
|
|
|