EVE Technology Lab

So how does it work later while running it since Yapeal requires one then as well but it can be blank. You do know it can pull all the settings from your config/yapeal.ini file right without having to use the command parameters? Maybe you've missed it in this thread or in the CHANGELOG but the scripts in install and yapeal.php itself have had a overhaul that added some better command help etc. Might try createMySQLTables.php --help to see what is new.

Yeah sounds like you were having some kind of database connection error there that cleared itself up. You might make sure the settings in my.cnf are right.

It doesn't do that but in the help message it tells you the default order which is util, account, char, corp, eve, map, server. So it's in alphabetical order except for util because each of the other sections update tables in it so they have to exist first. You can also tell it to run just one or a couple by adding the optional --xml=util ... parameter.

It saves the queries it was trying to run into cache/ADOdb/*.sql one per section.

The part of ADOdb used to run them doesn't really let you know just if it worked or not.

Edit: Also be nice to see you in chat again the evephp is gone until I find a new place to host it but I'm still around so convo me.

Dude, this is pretty damned sweet. At first, when I looked at this entire project I thought it was another PHP framework that I had to use in my own PHP code. Instead, I found out that it drops data directly into a database for me. Perfect. :]

I was a little frustrated at start when I ran the [php yapeal.php] script that I didn't see much activity in the database. I looked at the charAssetList after running the script and noted that it didn't add anything. After mucking around, found that I had to enable the option in the utilSections. I don't remember reading that anywhere. :( I have not had the chance to dive into the rest of the code yet, but maybe on the Wiki you could set aside some hints on how to get the ball rolling from a brand new install? Personally, I'd like to see a HINTS/TIPS section that'd give up some details on raw SQL queries to get some data out.

I've been working on coming up with a new Asset Manager (Since HeavyDuck isn't really doing much with his, and the old API system is going to be going bye bye, AND his UI is looking dated - NO OFFENSE!), and found your link about how things are done with the nested rowsets. Very VERY facinating (and new to me) method to say the least. The question I do have though is why you chose to go the route you did with this method of containing the data? The concept I get after looking at the external wiki you linked to, and its quite clear in my head, but, isn't it a bit overboard?

What I mean is, since a single item can only be placed in a container, on a ship, in a station, in the solar system, in the constellation, in the region, in the universe, that single item has a parent which is the container, and that container has a parent which is the ship, so on and so on. Standard Primary Key to Foreign Key relationship. No need for even an additional table since its a one to many relationship (But then again, a many to many relationship is just with an additional table linking O2M and M2O.)

Using your particular method (Which I am NOT putting down), if I wanted to find out what items I own are in a station, I'd first do a query to find all distinct itemID rows in a particular location. Now I'd make another query and find out what items are in that station, including GSCs, SWH, etc. But this is where things kind of get difficult to sort out at least on thrashing the database (Something I wish to avoid doing)

Here's an example of how I'm conceptualizing the pseudo code;

I have a Mammoth. The typeID for the ship is 652. Doing a query against this typeID gives me a lft value of 204 and rgt value of 315. So now my next query would want to run against all fields between lft and rgt of 204 and 315 respectively. This returns a count of 56 items in my case. I know I have 4 GSCs sitting on this ship. Each of these four containers are going to have their own lft and rgt values. Thing is, being a fore-thinker, I know that I'm going to have to re-query, or ignore somehow, the result set from the first query.

select lft,rgt from charAssetList where typeID=652; --Query #1
-- Have a list of all my mammoths - Which is one. Returns 204 & 315
select * from charAssetList where lft>204 and rgt<315 where ownerID={MycharID}; -- Query #2
-- First several rows return lft+1=rgt
-- Skip a few of the result set, I now have the GSCs, so have to requery
select * from charAssetList where lft>227 and rgt<310 where ownerID={MycharID}; -- Query #x
-- Process this result set as usual
***

So now I'm stuck. I've already 'worked' on the items between 227 and 310 and now I have to "remember" that I've dealt with this particular set going down the rest of the rows from the query #2.

Am I looking at this right?

Yapeal has a problem where the log directories for log4php are not relative to the script execution root. Which is annoying to say the least. As it differs from how it originally worked.

Ok, no, I got it wrong. The config file has actually changed, and it meant that yapeal suddenly didn't work anymore, because I was using the old config file (and the new config file still doesn't count log directories relative to the script execution directory).

I just hope that this doesn't catch anyone else off guard.

Hi everyone and Happy New Year So I've been working on a couple things in Yapeal and decided I should push them out to everyone.

First Ruziel reported a bug in Contracts API with how Yapeal handled ones that hadn't been accepted or completed yet. The API sends empty string value for 'dateAccepted' and 'dateCompleted' so it needs to be changed to a NULL for the insert/upsert. This seems to now be fixed now.

I've also been trying a new development tool PhpStorm that another developer told me about and I've been trying out some of it's features. Your can get it from
http://www.jetbrains.com/phpstorm/
One of the things I've been trying out was a complete inspection of Yapeal with it's inspect code feature. I told different developer about it and he said he'd be scared what it would report if he used it on his own code I'll have to say when you get back a report with 8000+ things it found it wasn't much fun but after looking at it some I realized most of them were 'spelling' errors including name of variables etc. There were some actual spelling errors too in some of the comments and I fixed them but the other problems it found were a bit more interesting.

Most of the rest of the problems it found turned out to be in the other libraries I use like log4php, eac_httprequest, and ADOdb in ext/. I already know there were problems with ADOdb since every time I really take a look at it's code I shutter and get this overwhelming urge to either try fixing it or go hide somewhere because of all the problems that exist. It works very well and doesn't have any real 'bugs' as such but you can tell many people have handled it and it still has a lot of legacy code from the PHP4 days that it just hasn't been able to shake off yet. So the first thing was to exclude ext/ and a couple other things that are outside of Yapeal itself that I just use in development. So next I figured out how to filter out stuff I wasn't interested in for now like everything in ext/.
So after filtering I only had a little over 2000 with 1800+ being spelling stuff which can largely be ignored but it still does look great yet for Yapeal. Some of the rest were pointing out the limits of the inspection feature itself in understanding dynamically building SQL and understanding how I'm using the magic functions like __get() and __set() in a couple places which isn't surprising since I've had to explain it to more than a few people that had never seen them used before in PHP

In the end after the manual filtering I did find several minor problems that needed fixing like not initializing some variables correctly, and some unused properties in some classes which were easy to fix. I also found a few places where I could simplify some if/else statements at the end of methods etc. There are some additional things I'll be looking into changing as well but they more about doing things in simpler ways or breaking up some of the more complex tasks which is something that is always an ongoing process in Yapeal anyway for me

Over all Yapeal was fairly clean which made me very happy

So you can get the new fully inspected version from the Mercurial or archives.

version 12.001.1845

Yeah it looks like I broke something trying to fix something else I'll try to get fix out in the morning after I've had some sleep and figure out how it broke and how to fix what I was trying to fix

Hi Dragonaire,
I have tested yapeal yesterday and I do like how it works. Great job.
But I did not found what I was looking for, and it is data fetched from http://wiki.eve-id.net/APIv2_Char_ContractItems_XML
Was it me or there is no way to fetch the data with curent library?

Issue added.
I am already happy with yapeal importing API to my db. Looking forward for ContractItems added. Could you add table for the data to distribution now so I could use my scrips for data imports? Would add my own table, but i am afraid it will be different from yapeals and than I would have to fix other of related scripts and tables.

Forgot to ask...
Why you adding checks for running it on shell? I have webspace and db only. Comented check on yapeal.php, and now scripts runs on apache without any errors... Is there anything to be afraid using apache to start scripts?

Hello. I've just upgraded to last Mercurial version and I get this error:


Thanks!

Thanks Dragonaire