"unknown column" "missing table" "duplicate column" error / sql problems / SQLDriverLogFile < answer on 1st post of 1st page

[Kylroi]

Just to be sure, execute "SHOW GRANTS;" (via command line or GUI interface...at least my GUI can do it) and paste the result.

[Near]

Where do i do it? Mysql command line?

Again if you could just teamviewer this for me it would be so much better. Contact me on skype vernonleon090. 

[Kylroi]

For command line, you could execute: mysql -uroot -pascent -e "SHOW GRANTS;"

 

The line with "IDENTIFIED BY PASSWORD" isn't important. Just need to see the specific database grant listing.

 

As I believe I said before, to benefit other users that may run into the same problem, it would be best to keep the conversation here. Plus, if we run into a brick wall, you won't have to explain everything all over again when someone else tries to help. Public records are are a good thing, even if they do seem to take forever.

[Near]

 

Sorry if i'm retarded lol is that what you wanted?

And also idk if this is of any concern it appear that i may have 2 MySQL folders.

 

 

 

 

This is my other folder.

 

 

Edited February 14, 2014 by Near

[Kylroi]

Close, but not quite. The command I gave is what you run in a CMD command line window. When at the "mysql>" prompt, you should not need "-uroot -pascent -e" or the quotes. You do, however, need to end the query with a semicolon (.

 

You aren't retarded, but you are showing your lack of knowledge of SQL. You may wish to read up on that if you intend to run your own server. Trust me, that will help, despite what some others will insist. Luckily, the syntax (command structure) is quite simple.

[Near]

Here you go. 

[Kylroi]

You should have something like the following:

| GRANT ALL PRIVILEGES ON `world`.* TO 'root'@'localhost' WITH GRANT OPTION                                                              |
| GRANT ALL PRIVILEGES ON `characters`.* TO 'root'@'localhost' WITH GRANT OPTION                                                         |
| GRANT ALL PRIVILEGES ON `auth`.* TO 'root'@'localhost' WITH GRANT OPTION                                                               |

Your grants listing suggests an incomplete or improper MySQL setup.

 

Additional thought: In theory, your grants should be ok. My setup uses a modified version of the sql/create/create_mysql.sql file (changing the user and password as I saw fit).

[Near]

Okay, so how do i go about fixing this : lol sorry

[Aokromes]

That error is usualy incorrect db structure vs core. Wipe your world DB and pull source and import TDB plus the merge of all WORLD updates, if it's your 1st instalation import also the base for characters and auth databases WITHOUT apply any AUTH or CHARACTERS updates.

[Deathicon]

Hi all,

 

I'm completely new to this project, and so far I very much like what I see. I am a developer myself and I thought it would be fun to join in. I'd like to work on the latest 4.3.4 core. So I have a question... I've read all the tutorials to get a build working that is sync with a specific version of the core, but what if I wanted to actually use the latest core version? Its not clear if I need to install the updates from TDB, or if I should only install the updates found in the core? In any case, I'm guessing I need to start from the latest Full-TDB-5?

 

Thank you.

[Kylroi]

If you're familiar with both C++ and SQL (MySQL specifically), you should be capable of using the updates from both the TDB repository as well as the updates from the core repository (assuming that you stick with the 4.3.4 branch...using the updates from the master branch would certainly mess up the database contents). There will be certain conflicts, but they will be easily filtered out by someone familiar with SQL. From there, you will find plenty of erroneous and missing functionality which you are more than welcome to contribute towards core and/or database development. All that is asked is that you follow the coding methods and SQL structure that is detailed (I forget where, but I think that's all mentioned on the forums here).

[Deathicon]

Ok cool I think I figured it out. There was a lot of errors in the SQL updates, that was kind-of a lot of work to fix them, but now I think I have a clean TDB that is sync with the latest 4.3.4 branch.

[Aokromes]

No, there are not errors on TDB updates, if you "fixed" errors on TC 4.3.4 repo you very likely fucked your db even you see your core running. Wiki is clear DON'T apply sql/updates/world files from TC 4.3.4 repo.

[Kylroi]

Forgive me, but many of the "I can't get worldserver to run" posts are a result of people doing EXACTLY what the wiki says. Meaning, they don't apply the updates from the TC 4.3.4 repository, so the server fails to work. They can't ignore that update tree AND still run the server. So, how about amending that "don't use" clause to list the required exceptions?

 

For the record, I recently created a test world database. I started with the 434.05 full, applied the TDB updates, then applied all of the TC 4.3.4 world updates. I just wanted to see what the errors were. I seem to recall that there was only 3 or 4 (if that many, actually) "errors" that I filtered out. The only errors I saw were dealing with a table that was removed (it was something about creature AI). I can't speak for any other conflicting changes, though (i.e. updates that actually reverted things to pre-Cata settings). Is it possible that the "*434.sql" (102 of those as of rev adc4b3b46b0d) files are safe to use? I seem to recall that none of those had to be excluded in my test.

[Aokromes]

Wiki also states to clone TC revision of the hash of the last sync. The only "safe" files to apply of TC repo are the ones altering db structure or creating new structures.

[Kylroi]

Wiki also states to clone TC revision of the hash of the last sync. The only "safe" files to apply of TC repo are the ones altering db structure or creating new structures.

 

Excuse me? Do you realize that you effectively contradicted yourself there? If TC and TDB are in sync, there shouldn't be any sql updates from TC at all. Otherwise, anything that changes the DB structure would, supposedly, break that revision of the core. Or, are you saying the TDB repository is not as perfect as you guys keep insinuating?

[Aokromes]

I say that TDB repo is outdated an wiki states to stay on TC revision of last TDB sync.

And no, i don't contradicted myself, i simply answered the question and the incorrect affirmation on a single line.

[Kylroi]

I say that TDB repo is outdated an wiki states to stay on TC revision of last TDB sync.

And no, i don't contradicted myself, i simply answered the question and the incorrect affirmation on a single line.

 

Fair enough. On the same line, however, separate concepts tend to blend together. You may wish to keep that in mind for future posts.

 

Just so this is available for others to find without asking it again and again:

• What exactly is the point of the sql updates in the TC repository for the 4.3.4 branch?
• Why are there updates specifically flagged 434 in the filename if they are still not to be used?
• Why are there ANY updates in the 4.3.4 branch flagged with 335 in the filename?

I believe that having those questions asked and properly answered will help eliminate many of the threads created as a result of DB creation errors. Surely, you can agree with that, especially with those 335/434 files being available even when staying in sync with the TDB repository.

[Aokromes]

1 and 2, they are temporaly there.

3 it's result of merging branches.

4) http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/#entry42704 and still we have people asking the same question every time.

[Kylroi]

1 and 2, they are temporaly there.

3 it's result of merging branches.

4) http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/#entry42704 and still we have people asking the same question every time.

 

In other words, 1-3 are all the direct result of lazy developers. Fair enough. Before you take offense to that, what else would you call a developer that pushed sloppy content not meant for public use to a public repository? Temporary? Why was that content even pushed out? It can be shared via some other method that isn't revealed to the general public. If you guys don't know that, you really aren't qualified to work on a project such as this. I have code of my own that isn't ready for public use. It's not on my repository or published in any way because I don't want someone getting upset by it not working as expected or reverting functionality that they didn't want.

 

As for 4, I did perform a search relevant to the updates and 4.3.4, but it either wasn't listing that thread in the results or it was very low on the list (on a secondary page, maybe). However, "4.3.4 sql updates" had this thread as #2 on my results (#1 is a closed thread that doesn't answer the issue). That was a search for the entire site, not just this specific forum. Still want to say that using the search will answer perfectly every time? Don't be a fool and say "yes". That search term is pretty specific on the issue and should easily catch any thread mentioning the question/problem.

[Aokromes]

No, 1-3 is not direct result of lazy developers, those files must be there for people with knowledge of how to do properly things.

Well help and suport forum have this description linking to that thread " Most of your questions about instalation problems have the answer -- -- -- HERE -- -- --"

[Paradox]

+Kylroi I see by many of your comments that you don't know how things around here work, but, one thing I can tell you will never change (because I have tried for years to change it) the Trinitycore repos are NOT public releases, they are dev repos that the public has access to, and, as such, the devs have no particular responsibility to ensure that anyone will be able to compile or run anything from them.

[MrSmite]

No, 1-3 is not direct result of lazy developers, those files must be there for people with knowledge of how to do properly things.

 

And... this is the question I've been asking al along: where do people who don't know how to do things properly learn how to do things properly (when the guides seem broken)?

 

The standard answers are:

• If you can't figure it out, you shouldn't be running a server
• That branch is in alpha so it's not supported

both of which contradict the whole methodology behind an open-source, public repo. It may not be ready for public use but there should be a modicum of support for potential developers who can't get it running. Otherwise just mark the repo private until its ready but then you lose potential developers and testers.

[Aokromes]

No, the guides aren't broken, they state for 4.3.4 branch you must stay on the last sync revision. Also if you have low knowledge of sql (like myself) you can make yourself the core work on 4.3.4 head, it's not hard at all to start core and look the startup errors asking you for sql structure/new tables, if with that they can't figure what to do, i must say sorry, stop using computer because you are to stupid to read.

[McBitter]

First of all, developers who actually know how to code can easily figure out any code and SQL errors. I know this based on the experience I've had with systems that I had zero knowledge about, but had the ability to actually write code from scratch. It would be all better to stop bitching about useless things, if you personally aren't the coder (SQL "devs" are not coders... really...).