Syntax Error on SQL import « MediaDrop Community

MediaDrop Community » General Discussion & Feedback

Syntax Error on SQL import

12 posts Started 14 years ago by tinycg Latest reply from Anthony Theocharis

No tags yet.

tinycg
Member
Posted 14 years ago

I'm new to setting up MediaCore and I continue to receive errors either through a command line import or web interfaces like phpMyAdmin stating 'You have an error in your SQL syntax;'

phpMyAdmin reports that its on line 1, and some googling seems to depict that its an issue with the delimiter, however my version of phpMyAdmin doesnt appear to offer a change in the delimiter as depicted in several online tutorials.

the command line also reports a similar error
"ERROR 1064 (42000) at line 589: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT CHARSET=utf8' at line 7"

Any help would be appreciated, looking forward to getting this setup and trying it out.
Nathan Wright
Maintainer
Posted 14 years ago
Thanks for bringing this to our attention. For now you can edit setup.sql: find line 595 and remove the AUTO_INCREMENT word. The line should read:
```
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
```
You can also get a fixed setup.sql from our Github repository.

Cheers, Nathan
86me
Member
Posted 14 years ago

Which leads to more errors...

I removed the AUTO_INCREMENT part and am now facing:

ProgrammingError: (ProgrammingError) (1146, "Table 'mediacore.topics' doesn't exist") u'SELECT topics.id AS topics_id, topics.name AS topics_name, topics.slug AS topics_slug, (SELECT coalesce(count(*), 0) AS coalesce_1 \nFROM media, media_topics \nWHERE media.id = media_topics.media_id AND topics.id = media_topics.topic_id AND (media.status & %s) = 0 AND (media.status & %s) = %s) AS published_media_count \nFROM topics \nHAVING published_media_count >= 1 ORDER BY topics.name' [1, 2, 2]

setup.sql file still seems incomplete. I tried some of the sql files in database/chages of git, but that is a disaster, causing endless errors just as you think you're on to something.

So what's the deal guys? I have yet to see a fully working release. I am running python 2.5, MediaCore 0.8rc1, basic slackware setup, nothing exotic.

If someone could supply a working setup.sql file, it would be much appreciated. I'm sure the new code is great.
Jeremy
Community Manager
Posted 14 years ago

We will be looking into this today.
Nathan Wright
Maintainer
Posted 14 years ago
68me, are you sure that's v0.8rc1 you're running? Because the query that's causing that error was removed when we refactored the frontend UI.

If you're indeed running against 0.8rc1 the only thing I can imagine causing this problem is an outdated .pyc file somewhere. You can delete all the pyc files within your mediacore install by:
```
cd MediaCore-0.8rc1/mediacore
find . -name '*.pyc' -delete
```
If you haven't added any data to your database yet, I'd also recommend deleting it and starting fresh with the latest setup.sql file. This setup.sql file is completely up-to-date so there's no need to run any of the scripts in ./database/changes — those scripts are intended only for those who want to track the development trunk between official releases. If you've run those scripts on top of the latest setup.sql file there's potential for all kinds of problems.

Hope that helps.
86me
Member
Posted 14 years ago

Are you guys developing on OSX? If so, I think that there is some inconsistencies. Shouldn't make a difference, but maybe.

I don't know why my pyc files would be bad when I get these errors on the first try.

You say that the setup.sql file is fine, then why does this topic exist?
Felix Schwarz
MediaDrop developer
Posted 14 years ago

Actually I was able to get it running on Linux (Fedora 12). However I found a couple of issues with just a few minutes of testing, see http://groups.google.com/group/mediacore-developers

I guess it's time for the simplestation guys to learn that unit+integration tests are not something you can leave out if the customer does not pay for it (imho customers never pay for quality separately, they always assume you deliver high quality, regardless of what they paid).
tinycg
Member
Posted 14 years ago

My issue was corrected upon making that change, I've got some other issues, but I dont think they are related to the sql import, ala 404 error right now trying to get the alias to work within the vhost.conf.
Anthony Theocharis
Key Master
Posted 14 years ago

86me:
Nate suggested to clear your .pyc files because the error you're experiencing only exists if you're executing an old version of the code. Did you download the 0.8rc1 tar.gz release, or are you using git? If you're using git, the problem is likely that "git fetch" isn't actually fetching. When I pushed the tag for 0.8rc1, I pushed a slightly different repository. If you were up to date in git before that, it will complain that the fetch is not fast-forward. The simplest solution is to check out the repository again (you can also do something like "git branch -r -D origin/master; git fetch; git pull origin master;"). This will ensure you have the latest code.

Re. why this topic exists: I made a mistake when putting together the 0.8rc1 package. I missed out the syntax-fixed setup.sql file. Nathan has since added the correct .sql file to the git repository.

Re. our environments: We do develop on OS X (10.4-10.6), but getmediacore.com runs on CentOS 4.

Felix:
You're right. We really should've insisted that tests be included in development. My focus over the next few weeks is going to be fixing bugs and writing tests. As soon as I get a baseline test suite written, any help on that front will be very welcome.
Anthony Theocharis
Key Master
Posted 14 years ago

tinycg:
What does your .conf look like?

[EDIT:] on second thought, maybe start a new thread to discuss the .conf.
Felix Schwarz
MediaDrop developer
Posted 14 years ago

Anthony: Can you please give "us" early access to the stuff you're working on? I'll add a couple of unit tests for my own stuff so maybe we can share some code...
Anthony Theocharis
Key Master
Posted 14 years ago

Sure, Felix. I'll push a 'tests' branch to github when I start work on it.

RSS feed for this topic

Reply

You must log in to post.

Community Forums

Syntax Error on SQL import

Reply