open All Channels
seplocked EVE Technology Lab
blankseplocked Yapeal PHP API library (revision 1203 branches/keys/)
 
This thread is older than 90 days and has been locked due to inactivity.


 
Pages: first : previous : 1 2 3 4 [5] 6 7 8 9 ... : last (24)

Author Topic

Iskandara Cho
Posted - 2009.01.16 22:11:00 - [121]
 

Edited by: Iskandara Cho on 16/01/2009 22:11:06
Well, I guess I'll just toss my work thus far. Ah well.
Still, its nice to know we'll have an installer soon.

Also check Google Talk not gchat, they are different things.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.16 23:39:00 - [122]
 

I'll take the blame on this one when you both said something about installer I wasn't paying as much attention as I should have been and realize it was two different people not just two different characters and the some person Embarassed Since one seems to be aiming at IGB and other normal browsers it's not really bad to have two people working at it. I'll let you guys decide if you want to combine your work or keep do parallel development and then I'll cherry pick from both after you have both finished. Let me know what you guys decided or maybe we can all get together somehow and talk it over.

A little point of interest on the number of connections Yapeal was making to the database server and how the new code I'm working on effects it. In testing I've getting an ~8 to 1 decrease in the number of new connections Shocked with more then one corporation using it that number should go higher because of more reuse of connections with balances, journals, and transactions etc. This should make anyone on a shared hosting happier since lots of DB connections can really lag you out if the DB server is overloaded. After a couple more tweaks (I seemed to be low on my quota of bugs today need to make a few more for myself Razz) and some more testing I should get this out later day.

Iskandara Cho
Posted - 2009.01.17 00:21:00 - [123]
 

Since IGB pages work out of game as well, there is no reaon to duplicate the work. I'll just take the hit and look forward to the install script being done.

Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.01.17 01:33:00 - [124]
 

Oh I didn't know that some one was making an installer as wellShocked

Well can say that the one I'm doing right now is in first priority based on the IGB and you can not load it offgame since there is checkers that cheks if you are insite eve and if not, tells them that the installer can only be reached from the ingame.

However, I have planed to implement the outgame suport as well but I just want the IGB to work first.

Why I'm doing the IGB first is that it's the fastest and easyest way to get the character ID and name as well as the Corp ID and name.
With a trustet site request you can get those variables without having to fitling around the api and cache the character and charactersheet XML to pull those information out.

Anyway, the progress with the installer is allmost done since alle the check for compability on the webhost have been done as well as folders and file write premission. the only part is missing is the fun part where I create the database and the yapeal.ini file.
A beta will be done within 24 hours I think.

Just keep in mind that the outgame browser is planed, but first when the IGB part is done since the outgame browser takes a little more time to implement. I'm a little rusty on the API part so I need to refresh that, for the outgame support Very Happy

Dragonaire I have removed the Debugging function as you mentioned in the email. I has as well removed the Database-server part since it will be implementet as a standard activ=TRUE as well with the Util DB.

1 question thou.
all the comments that are in the yapeal.ini-example would you like to have those implemented as well or is it okay with an raw ini file without the descriptions ?

Kind regards
Satis

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.17 02:28:00 - [125]
 

Really sorry for the mix up on this Sad

Satis Iqulenax think you could drop the commits and just have one at the top referring them to the example file and maybe the wiki pages instead that should cover it but if anyone else has an idea about this speak up. Make sure to include the new fields for version etc that I added I'll need that for some updating stuff I'm thinking about as well as when people ask for help and send me their logs.

Ok Iskandara Cho guess this will leave you more time to work on the docs we also talked about instead which is something that needs done just as badly as the installer did Smile

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.17 08:36:00 - [126]
 

OK new version is out with the improved DB connection code. I'm see 9:1 decreases in number of new connections vs the old code Shocked I knew it would be an improvement but didn't expect that much really. I might be able to tweak it a bit more but not to worried about it now for some reason Wink I'll move on to the other things I've had planned to make adding new APIs easier I think for now.

current version 464
Get it while it's hot!

Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.01.18 14:58:00 - [127]
 

A little update on the Yapeal Installer.

I might just skip the IGB installer and just have the normal browser installer, since I found a smart way to get the characterlist in JavaScript so gettimg the info on a character just depends on what PAI setup you make.

I'll make this so if you try to open this site in the IGB it will just give you a link that will pop out of EVE and open the Yapeal Installer in a normal browser.
Thai way I don't have to make my script 2 times, one with javascript support and one without since IGB does not support JavaScript.

Status:
  • the grafical UI is done

  • The requirement test is done

  • The basic cofiguration input site is done. There will be more advanced setups like chosing different databases to each setup groups

  • Working on database creation right now.

I think that's that for now.

//Satis

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.18 19:30:00 - [128]
 

Satis Iqulenax - Sound good looking forward to having a go with it when you have it finished.

On other news some of you may have noticed I've had lots of problems getting out working versions of Yapeal lately. Part of is some software I was try working in unexpected ways when merging branches back into the trunk but mostly it was because of how I was working and testing the code. The way I was doing it tended to mix things like the config file from one branch or the trunk with the code from the other etc.
Needless to say that just doesn't work well. So after someone got on me the other day about it I started making some changes to how I've setup my testing that should help prevent that from happening.

Another problem I have is because I only have 3 of my characters and one small alt corp to test with I just can't test the code like it needs to be. To try to solve the lack of ability on my part to test stuff I'd like to ask for some of you to help out as alpha/beta testers for me so the code can be more fully tested before I bring it back into the trunk.
One thing I need from anyone that wants to help out as a tester is you most have an hour or two every one or two days when you can try stuff and either report back what happened or you can be on Google's IM with me when you are testing so I can ask questions and have you try stuff. I'll try to put up some more info on the wiki or somewhere about it but for now if you're interested in giving me a hand with this sent me an E-mail to either the e-mail in the code or my alt's E-mail dragonrun1 over at Gmail

Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.01.24 20:07:00 - [129]
 

Okay people.

After working together Dragonaire I have made an Basic Yapeal Installer.

It out now together with an version of yapeal that should be stabel.

the installer is working with both JavaScript enabled and disabled but the one with most install steps will be the one with no JS active.

This will make it easyer for people to setup Yapeal and will be able to run it without having problem with manual setup.

In the future there will be a more advanced installer that will be able to handle setup of multi databases as well as setup table prefixes so you don't mis tables together.
There will allso be the option to input a password from the installer after Yapeal have been setup so you can edit your setup without having to remove the yapeal.ini config file.

To download yapeal in the most easy way is to grab it from the SVN.

For you who don't know how to do that, here is a little tutorial on doing so in windows.
  1. Download Tortoisesvn

  2. Install Tortoisesvn

  3. Create a folder where Yapeal should be placed.

  4. Right click on the folder and chose: SVN Checkout

  5. In the Url you input: http://yapeal.googlecode.com/svn/trunk

  6. Now press the OK button and it should get the latest version of Yapeal.

  7. Now each time you want to update to the latest version just right click the folder and chose: SVN Update and it will automatic update to the latest one.


I think that's all.

Kind Regards
Satis Iqulenax
Yapeal Member

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.24 21:34:00 - [130]
 

Thanks Satis Iqulenax for all the hard work on the installer know it took a while longer to finish it then we expected but it works well. Everybody that's been having any problems understanding how to setup Yapeal should be very thankful now to you for this Smile

Now on to other news while not helping Satis Iqulenax with the installer now and then I've been working on a branch where I've making some changes that should make everyone happy when I'm done. I've been working on the code so that adding new API will be much easier to give you an example of how much easier within a couple hours of get the first API convert I decided to add a few new ones just to test it and I ended up with several from the map working and also convert the ones I had before in eve over and working. So in the time it would normally take to do one I did 7 Shocked and have another mostly done Very Happy while adding another section (area) for maps that Yapeal didn't do before. This is something I'd been want to get to for over two months now but other things have had priority.

I'm also starting to add and test the table prefixing code as part of the change over in code while I'm at it which brings up another change I have been thinking of making. I thought I'd get some input from the people using Yapeal before making this change since it might cause some problems. The change is to no longer support having each API section in a different DB. To better understand what I'm talking about go over to the main Eve-Dev API page. The sections I talk about are like where you see Account, Character, Corporation, etc. As it is now in Yapeal each one of those can be in different databases with different user/password and other settings. This does let there be some nice flexibly but also makes for a more complex configuration to maintain and use. By dropping this ability to use multiple database it would greatly simplify the yapeal.ini and along with some other changes I'm looking at could get it down to maybe less then six settings while adding a bunch of per character and per corporation settings for which API you actual want. So for example now if you enable a character in RegisteredCharacter and Yapeal had stuff to get the SkillInTraining API it would interfere with your EveMon Sad With some changes including dropping the multiple table stuff that is I believe not used by anyone it'll greatly simplify add per character/corporation settings on APIs so the APIs for things like SkillInTraining, Killlog can be added to Yapeal but turned off so they don't interfere with EveMon and Killboards you might want to use.

Okay I'll stop there for now before this gets any longer and see what everyone thinks of making the changes.

Sondrou Xi'Tral
Gallente
Priory Of The Lemon
Atlas Alliance
Posted - 2009.01.25 07:58:00 - [131]
 

Ok, I just used the installer (very nice btw), and everything seemed to install fine. However when I point my browser to backend/eve-api-pull.php I get the following message:

Notice: Yapeal version 464 (beta) 2009-01-17 03:16:35 in /home/u5/methos237/626/html/api/inc/common_backend.inc on line 55 Fatal error: Call to undefined function spl_object_hash() in /home/u5/methos237/626/html/api/class/YapealApiException.class.php on line 75

Buzz AU
Posted - 2009.01.25 11:44:00 - [132]
 

Notes regarding the Installer:
Quote:
Welcome to Yapeal Installer.
This installer will setup Yapeal EVE API Library to be runned on your site.
The setup will check if your web host has the requirements to support this library.


It should be "run on your site", not "runned on your site"

On the "success page"
Quote:
The setup is done.
You can now run the backend/eve-api-pull.php to cache all the data


Maybe make the "backend/eve-api-pull.php" a link?

Just comments. It is fantastic and a LOT easier. Great job



Buzz AU
Posted - 2009.01.25 11:50:00 - [133]
 

Edited by: Buzz AU on 25/01/2009 12:10:47
I get the below when trying to pull the data, I have set the permissions on the file and folder to "777", but still get the same.


Quote:
Forbidden

You don't have permission to access /Yapeal/backend/eve-api-pull.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Apache/2.2.10 (Unix) mod_ssl/2.2.10 OpenSSL/0.9.8i DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at www.mysite.com Port 80


This was caused by the .htaccess in the backend folder, which has a "deny from all"

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.25 14:41:00 - [134]
 

First off the reason there is a .htaccess in backend/ is YAPEAL IS NOT A WEB APPLICATION It is a library you use to make a web application with but YOU ONLY RUN YAPEAL FROM A COMMAND CONSOLE, OR CLI as it is know in PHP. The ONLY part of Yapeal that is made to be used as a web page is the installer. Everything else in it is made to be used from the CLI.

Buzz AU
Posted - 2009.01.25 18:25:00 - [135]
 

Is that to say, we shouldn't run it using a normal cron job?

Johnathan Roark
Caldari
The Graduates
Morsus Mihi
Posted - 2009.01.25 18:29:00 - [136]
 

Originally by: Buzz AU
Is that to say, we shouldn't run it using a normal cron job?


That would be running it from a CLI, so yes

Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.01.25 19:34:00 - [137]
 

Originally by: Buzz AU
Is that to say, we shouldn't run it using a normal cron job?


Yes you can run it as a cronjob and it is ment to be runned as a cronjob or on windows server a schedul task.

What Dragonair men't is that you should not run eve-api-pull.php from a webbrowser.
That's why there was put an .htaccess file in that directory :)

//Satis

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.25 22:35:00 - [138]
 

Okay I guess I'm making to many assumptions here that people understand some things that apparently they don't so I try to clear some of them up for everyone.


  • CLI or Command Line Interface is a generic term that the designers of PHP use to describe any console type interface i.e. NOT windowed or web. On most Unix systems this is normal sh, on Linux it's Bash or one of several others if the user changes it. With Windows systems you have cmd.exe which you can usually access through the classic start menu by Start > Run and typing in cmd and clicking OK.
    If you use anything like SSH to get to your hosted web server you are also run a CLI, usually Bash, with the input and output in effect redirected to your local machine over an encrypted connection.

  • Cron or also know as crontabs is a system available on most Unix/Linux to run CLI programs/scripts for a user at different starting times and intervals. Generally only the interval part is used where it can be anywhere from 1 minute to hours, days or clear out to years in the future.

  • Schtasks provides the same basic functionality as crontab does for Unix/Linux systems.

  • Yapeal short for Yet Another Php Eve Api Library is a CLI PHP5 script that gets information from the Eve XML API and puts it into a MySQL database. A web based installer has also been made for it to help people get started with it but the main script is only made to be run from a CLI or as a crontab job.



Hope this is useful to people and helps make some things clearer.

Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.01.25 22:41:00 - [139]
 

Edited by: Satis Iqulenax on 25/01/2009 22:41:40
Okay I have just made 3 guids in the Yapeal Wiki.

  1. Setup a webserver on windows using Wampserver

  2. Install Yapeal on your windows webserver

  3. Guide to setup task scheduler for Yapeal in windows (Like cronjob)


Hope they will be of some use for those who want to testout Yapeal on there own Windows PC

//Satis

Buzz AU
Posted - 2009.01.25 22:47:00 - [140]
 

In that case, change the final step in the installer, to not say "now you can go to /backend/.."

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.25 22:51:00 - [141]
 

Yeah the installer is in a raw Alpha/Beta state but we thought it was useful enough it was worth getting it out for people to use as we polish it and do a newer version with some more features.

Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.01.26 18:51:00 - [142]
 

Originally by: Buzz AU
In that case, change the final step in the installer, to not say "now you can go to /backend/.."


Both the welcome page and the end page should now be updated and can be updated from the trunk now :)

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.01.28 23:22:00 - [143]
 

Just ran across a web page that anyone try out Yapeal on Windows and having problems with PHP might want to take a look at.
http://www.corephp.co.uk/archives/36-A-Guide-to-using-PHP-5-Extensions-on-Windows.html

Cryten Jones
Gallente
Advantage Inc
The Matari Consortium
Posted - 2009.02.05 17:18:00 - [144]
 

Hi,

Nice work here! Just learning how all the dump tables work and this API is making my life easier * 1000 to get my head around it all!

Could anyone tell me what the lft and rgt column in the assets table are? I can't see them anywhere on the api documentation!

Also, how does yapeal deal with the Item X is inside Item Y? The xml provides a 'contents' value but as far as I can see yapeal just sets assets locationID to the same as their containers..is this right?

Thanks

-CJ



Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.02.06 02:00:00 - [145]
 

Originally by: Cryten Jones
Could anyone tell me what the lft and rgt column in the assets table are? I can't see them anywhere on the api documentation!

Also, how does yapeal deal with the Item X is inside Item Y? The xml provides a 'contents' value but as far as I can see yapeal just sets assets locationID to the same as their containers..is this right?

Thanks

-CJ


Hi CJ.

the 2 question you made is actually related to each other.
the lft and rgt is hierarchical data and is a more advanced method to get what's inside a container or what a ship is fitted with or what is in a station.

to find out more about this, read in the Yapeal wiki in this section: hierarchical data
Read and use the links in there and your question will be answered :)

Kind Regards
Satis Iqulenaz
Member of
Yapeal Project: Installer/Setup

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.02.06 05:46:00 - [146]
 

Edited by: Dragonaire on 06/02/2009 06:49:14
Something that might give everybody a better understand of some of the power that nested sets gives you here's some examples.
Finding all corp offices (typeId=27) with assets:
Quote:
SELECT `locationID`,`lft`,`rgt`
FROM `AssetList`
WHERE `typeID` =27
AND `ownerID`=1234567890
AND (`rgt`-`lft`)>1
ORDER BY `lft`

which gives us something like:
Quote:
"locationID","lft","rgt"
"66007616","8","85"
"66008840","86","605"
"66008831","606","925"
"66011279","926","1241"
"66008453","1242","1523"
"66013316","1528","1769"
"66010271","1770","1901"
"66000173","1902","1907"
"66008450","1908","3273"
"66008324","3314","3391"
"66003473","3410","3499"
"66010529","3504","4815"
"66007361","5288","5305"



To get a list of all the assets from all the hangers in the first office:
Quote:
SELECT `typeID` , `quantity` , `flag` , `lft` , `rgt`
FROM `AssetList`
WHERE `ownerID` =1234567890
AND `lft` >8
AND `rgt` <85
ORDER BY `lft`

which gives us something like:
Quote:
"typeID","quantity","flag","lft","rgt"
"17912","4","118","9","10"
"11132","1","121","11","12"
"444","1","117","13","14"
"22542","3","117","15","16"
"18618","1","118","17","18"
"18618","3","118","19","20"
"25934","1","117","21","22"
"18618","1","118","23","24"
"578","1","117","25","26"
"17482","1","118","27","28"
"17482","1","118","29","30"
"652","1","119","31","78"
"1319","1","13","32","33"
"1319","1","11","34","35"
"1319","1","12","36","37"
"12058","1","19","38","39"
"25861","1","28","40","41"
"1952","1","23","42","43"
"17471","289","5","44","45"
"25592","2","5","46","47"
"25590","2","5","48","49"
"2032","1","21","50","51"
"6573","1","22","52","53"
"17459","18","5","54","55"
"17470","32","5","56","57"
"1228","91","5","58","59"
"17463","41","5","60","61"
"1224","221","5","62","63"
"17452","23","5","64","65"
"17464","285","5","66","67"
"17460","36","5","68","69"
"1230","150","5","70","71"
"25601","5","5","72","73"
"25599","2","5","74","75"
"1319","1","14","76","77"
"17482","1","118","79","80"
"22557","1","118","81","82"
"482","1","118","83","84"


Now we'll look at the stuff on the Mammoth (typeID=652):
Quote:
SELECT `typeID`,`quantity`,`flag`,`lft`,`rgt`
FROM `AssetList`
WHERE `ownerID`=1234567890
AND `lft`>31
AND `rgt`<78
order by `lft`

which gives us it's fittings (flag>=11 and flag <=34) and cargo (flag=5):
Quote:
"typeID","quantity","flag","lft","rgt"
"1319","1","13","32","33"
"1319","1","11","34","35"
"1319","1","12","36","37"
"12058","1","19","38","39"
"25861","1","28","40","41"
"1952","1","23","42","43"
"17471","289","5","44","45"
"25592","2","5","46","47"
"25590","2","5","48","49"
"2032","1","21","50","51"
"6573","1","22","52","53"
"17459","18","5","54","55"
"17470","32","5","56","57"
"1228","91","5","58","59"
"17463","41","5","60","61"
"1224","221","5","62","63"
"17452","23","5","64","65"
"17464","285","5","66","67"
"17460","36","5","68","69"
"1230","150","5","70","71"
"25601","5","5","72","73"
"25599","2","5","74","75"
"1319","1","14","76","77"


Notice that when we selected all the assets in the office it included everything on the Mammoth as well.

Hopefully these examples will help everybody to better understand how to work with nested set as used in the AssetList APIs.

Satis Iqulenax
Amarr
Free Imperial Vikings
Posted - 2009.02.06 14:12:00 - [147]
 

Originally by: Dragonaire
Something that might give everybody a better understand of some of the power that nested sets gives you here's some examples.


I just took the opportunity to take your small guide Dragonaire and paste it in the wiki on Yapeal Wiki.

The link is here: Small and simple nested sets guide

Kind Regards
Satis

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.02.10 20:51:00 - [148]
 

Hi all it's been a couple weeks since I've really posted about any changes or updates on Yapeal so I thought I'd let people know what's been going on. I've been in the process of doing a much needed re-factoring on all the code that will make it much easier to maintain and add to. Many of the ideas for the changes I've been kicking around for a couple months but was put on hold until I had more of the bugs fixed and what I considered the base set of APIs working. The old code though it worked had several problems with it that made it difficult to add new APIs especially by anyone other than me and sometimes when adding new APIs it would break others. It also had some limitations that made adding some requested features difficult or near imposable without changing a lot of code. I've also been learning a lot about how many site hosting locations setup stuff for their customers and where things I had done with Yapeal made it hard for many people to setup and use it. Given all the above I decided to 'crawl into a hole' so to speak and do a near complete re-write of much of the code.

Okay on to what this will mean for anyone using Yapeal which is all that most of you are interested in anyway Wink Here's a broad outline of some of the changes/additions to expect.

  • Table name prefixes. Many people are only allowed a single database at their hosting site so they need to have their applications and Yapeal tables all play nice together. I was also running into some issues with APIs using duplicate names on some rowsets which adding table name prefixes would also help solve.

  • Ability to use multiple database to store all of Yapeal's varies tables has been dropped. This allowed for many of the other changes to be done much easier and was believed to be a largely unused feature. With the addition of user settable table prefix name the need for this is believed to be largely mote now so it was removed.

  • There will be some changes to the database tables. All the table names have been changed to add a two part prefix the first part is user configurable and second part set internally by Yapeal.

  • Some new tables have been add for additional APIs or old APIs that have been expanded on to make them more complete.

  • Each API is now implemented as it's own class which solves many of the problems of changes to one API effecting others. This has also made adding more APIs easier and should make it easy for other programmers to understand how to add an API. That should mean not always having to wait on me to get around to adding new ones. This doesn't mean I won't be continuing to add APIs just that maybe I won't have to do all of them myself.Smile At least that is my hope anyway.

  • Some bugs and mis-features fixed. Probably added a few new ones but I've been do much more testing on this code then some of the code I've released in the past.

  • The yapeal.ini has had a major overhaul and been streamlined. Dropping multiple database table support was one of the main things helping with this but there were many other factors that made this possible.


Ok that should get you an idea what's coming. I hope to be finished with the conversions/updates and have finished all the testing I can do this week and be able to release everything into trunk for people to try out. I'll try to have a more detailed change list available when I release the code and probably have some instructions on what you'll need to do if you're upgrade from the current version of Yapeal.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.02.19 00:36:00 - [149]
 

Hi all so it took a little more than a week but someone else decided to have an extend downtime on me Razz but I've now merged all the changes into trunk for people to try. All current users be sure to read the updating.txt file in the root directory it has some important instructions on migrating your data from the old database tables into the new ones as well as some other information you'll need.

Please report any bugs you find. I've tested this revision more that many in the past but some bugs may have got through since I have limited resources to test some things with the characters available to me.

The currently supported API list on the wiki has also been updated for anyone interested.

revision: 572

Ramov Tinoga
Tinoga Enterprises
Posted - 2009.02.23 11:48:00 - [150]
 

Edited by: Ramov Tinoga on 24/02/2009 07:59:28
Dragionaire, thank you very much for the new framework! Very Happy

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 6 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?


Pages: first : previous : 1 2 3 4 [5] 6 7 8 9 ... : last (24)

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only