Chat with fellow EECMS users in the 'Database Error Occurred Error Number: 1146' ExpressionEngine community discussion forum thread. DB function failed with error number 1146 Hello, even when I saw several post about 1146 I am confuse I have created a menu link liked to the CB. A Database Error Occurred Error Number: 1146 Table '(database name).content' doesn't exist SELECT * FROM content WHERE id!.
You can watch a thematic videoFatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]  Access denied
Error namber 1146 - apologise, but
10.12.2 errors.Error Exception
This exception is the base class for all other exceptions in the module. It can be used to catch all errors in a single statement.
The following example shows how we could catch syntax errors:
Initializing the exception supports a few optional arguments, namely , , and . All of them are optional and default to . is internally used by Connector/Python to raise MySQL client and server errors and should not be used by your application to raise exceptions.
The following examples show the result when using no arguments or a combination of the arguments:
The example which uses error number 1146 is used when Connector/Python receives an error packet from the MySQL Server. The information is parsed and passed to the exception as shown.
Each exception subclassing from can be initialized using the previously mentioned arguments. Additionally, each instance has the attributes , and which can be used in your code.
The following example shows how to handle errors when dropping a table which does not exist (when the statement does not include a clause):
Prior to Connector/Python 1.1.1, the original message passed to is not saved in such a way that it could be retrieved. Instead, the attribute was formatted with the error number and SQLSTATE value. As of 1.1.1, only the original message is saved in the attribute. The formatted value together with the error number and SQLSTATE value can be obtained by printing or getting the string representation of the error object. Example:
is a subclass of the Python .
Error message: MySQL Error: Table 'databaseprefix_databasename.options' doesn't exist MySQL Error Number: 1146
If you get an error like the one abelow during an upgrade:
MySQL Error :
Database Error In SunShop 4.3.2 Installer: Invalid SQL: SELECT * FROM `options` where name='version'
MySQL Error: Table 'databaseprefix_dbname.options' doesn't exist
MySQL Error Number: 1146
Date: Monday 14th 2012f May 2012 06:18:39 AM
This usually means that the $dbprefix line in your include/config.php file is incorrect. Make sure that the line is commented or uncommented out depending on how you have it set up via MySQL or your hosting control panel.
For example, if you used "ss_" for your database but leave the line commented, it will lead the software to think your databases do NOT have prefixes and as such can't find the database you're defining.
Instead, make sure that line reads like the below:
$dbprefix = "ss_"; // Uncomment this line if this is a new install.
Adding the two slashes (//) in the beginning of that line "uncomments" the line.
If you're NOT using any prefix, that means you left the line commented during the initial installation. When you upgrade ensure that line retains its two slashes.
- 88 Users Found This Useful
Open, Free, Amazing
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
I’m working on a new site, using a fresh install of 2.7.2. Everything’s been going swimmingly (sort of), until now I went to edit some custom fields. When I click on a field name to do an edit, I get the following:
Using phpmyadmin, I see that there is in fact no “exp_grid_columns” table in the database. So what does that mean? Should I just create a table with that name? Not actually sure what’s involved with that….
I saw a bunch of 1146 error codes relating to the Comment module in the Forum, but this doesn’t seem to have anything to do with that (I even tried installing the Comment module).
I’m not really a MySQL person, so I’m not sure where to go from here. Any ideas?
Thanks in advance!
#eecms, #events, #releases
FYI - I have never been able to replicate this (I've seen it once or twice before). I'll dig into it some more and let you know what I find.
In the meantime, you could always restore your install from the backup (auto created on Windows). There should be another directory in c:\xampplite called open-audit-TIMESTAMP (substitute the timestamp for when you initially ran the upgrade). Delete c:\xampplite\open-audit. Rename the backup folder to open-audit. Remove your existing (broken) database:
c:\xampplite\mysql\bin\mysql -u openaudit -popenauditpassword -e "drop database openaudit; create database openaudit;"
Restore the old database:
c:\xampplite\mysql\bin\mysql -u openaudit -popenauditpassword openaudit < c:\xampplite\open-audit\db_backup_TIMESTAMP.sql
(substitute the timestamp for when it was backed up).
You may encounter issues with files in c:\xampplite\htdocs. If you do, post back and we can fix those as well.
I'll keep you updated with what I find.
I've posted yesterday an issue with an mySQL update syntax on CodeIgniter in here:
CodeIgniter – MySQL Error 1064 (Update table1 inner join table2(…))
But now after I solved that problem, another one come up. Now the update query doesn't know the new created table. But if I change to a select statement, it works smoothly.
For that reason I've decided to post the full script.
A Database Error Occurred
Error Number: 1146
Table 'pacsdb.STUDY_LIST_AUX,' doesn't exist
. = 'study_report.report_status' WHERE
. = 'study_report.study_iuid'
I've checked phpmyadmin after refresh the page and the table really exists and it contains the data from the select statement.Can you please tell me what mistake I did?