|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Mintoko
Gallente Nova Remnants
|
Posted - 2008.12.29 06:27:00 -
[1]
This is absolutely wonderful. I finally got it to work, but have a request...
I want to be able to add a prefix to the table names so that I can place them into my current database and still keep them together instead of having them spread throughout the list. I'm looking at the possibility of doing this myself, but will probably still be fiddling with it a lot longer than it would take you. :)
Perhaps, a default yap_ or something manually configurable.
|
Mintoko
Gallente Nova Remnants
|
Posted - 2008.12.30 01:46:00 -
[2]
Originally by: Dragonaire Mintoko - I've been looking at adding some kind of prefix to all the table names because some of the API re-use the same names in the rowsets but with different columns (fields) An example would be 'skills' in both the CharacterSheet and SkillTree. To add any kind of prefix though will require editing most the SQL queries in Yapeal since most places the table names are hard coded into the SQL Probably a bit of lack of foresight on my part but something that often gets overlooked when try to get something working.
I'm working on some changes to Yapeal that should make adding more APIs in the future easier and as part of that I plan on adding some kind of prefixing system so it's less of a problem. I'm not sure when I'll release these changes since it's very much in an early stage of development and I haven't even got any running code yet so best I can say now is it's on the list of things I plan to do
If you decide you can't wait and go ahead on your own and make something hopefully you'll share it back with us and maybe I'll be able to add it into Yapeal for everyone else that might have the same need.
I certainly will....I almost had it completely working, but made a change that crapped up the whole thing. I made two fresh attempts and think that I may be successful on the third attempt. I'll let you know.
|
Mintoko
Gallente Nova Remnants
|
Posted - 2009.01.14 02:33:00 -
[3]
I was going to do some whining that the api wasn't being pulled when setup as a cron job, but decided to try changing the permissions on the file before posting.
eve-api-pull.php had permissions set at 644, but would not work under cron until it was changed to 755. Of course, it may work with 744, but has not been checked.
The only other problem I had noticed the last couple days is that the server status was not updating, but is now working for some unknown reason. If the file permissions were responsible for this, I would think other api items would be affected, but none were noticed. |
Mintoko
Gallente Taedium In Perpetuam
|
Posted - 2011.07.20 05:10:00 -
[4]
Originally by: Dragonaire
Quote: Failed to execute schema for util Not all files processed correctly
Not sure why it does that, it sometimes happens to me too, but as long as DB and tables in util* get created it should be ok. If you want you can try running the cache/util.sql that is generated as well by script directly in MySQL just to make sure everything is all right. I believe in part I'm running up against some bug or limitation in ADOdb Data Dictionary. One reason a friend and I decided to branch the old project is to fix some know problems with it and try to add things to it to make it more useful for ourself in our other projects like Yapeal etc plus everyone else that might find it useful.
Anyway everyone please upgrade to revision 1176 and let me know if that fixes the problems with connections.
Previous revisions were giving me random multiple table creation failures. The latest revision only had one, char.xml. After attempting to run the tables with the cached SQL file, mysql reported the following:
Error Code: 1071. Specified key was too long; max key length is 767 bytes
CREATE TABLE yap_charAttributeEnhancers ( `ownerID` BIGINT(20) UNSIGNED NOT NULL, `augmentatorName` VARCHAR(255) NOT NULL, `augmentatorValue` TINYINT(2) UNSIGNED NOT NULL, `bonusName` VARCHAR(255) NOT NULL, PRIMARY KEY (`ownerID`, `bonusName`) ) ENGINE = InnoDB COLLATE = utf8_unicode_ci
I remember reading something about differences in key length between InnoDB and MyISAM, so I switched the engine and ran the query again with success.
|
|
|
|