Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #006013

  • 4 - High

  • Fixed

Issue Confirmations

  • Yes (0)No (0)
Photo

sql-files/ error when executing sql file

Posted by Hercules Bot on 14 June 2012 - 12:37 PM

Originally posted by plankt
@r16253+

The values were changed in some SQL files from 0 to NULL.

The columns however still have 'NOT NULL' defined.

Originally posted by Kenpachi
I'm really sorry. The imnport worked for me because I have a customized database.
Will be fixed soon and wont happen again. Sorry sorry sorry. @.@

Originally posted by manabeast
ya. me have problem executing item_db.sql . and i realize inside alot like #  < - only this empty thing.. if this problem solve can pm me the item_db.sql? urgent need.

http://rathena.org/b...em-dbsql-error/

pls pm me the fix one if you have tq =)

Edited by manabeast, 14 June 2012 - 01:12 PM.


Originally posted by Kenpachi
The item_db.sql is fine. It's PhpMyAdmin that sometimes can't handle commented (#) lines. I suggest to use the MySQL Workbench or the commandline tool instead.

But the NULL values in mob_skill_db that I commited are wrong and must be fixed ASAP. (I think can do it in the evening.)

Originally posted by manabeast
i remove the all the # infront. now no see error. is that ok one if i remove all those #?

Edited by manabeast, 14 June 2012 - 05:11 PM.


Originally posted by jysn
it's on mob_db.sql and mob_db_re.sql. got problem on NULL.

Originally posted by Bahmut
@manabeast
just search and replace every # with --. Because some versions of phpmyadmin don't like # for commenting lines.

Originally posted by manabeast
ok, thx bahmut. i keep this one for me future use.

Originally posted by Kenpachi
Fixed in [rev=16304]. Sorry again...