SEARCH YOUR SOLUTION HERE  

Unable to include #include


I am unable to include #include in C++ project under windows platform.

I am using Eclipse IDE. and i have added all the headers files MYSQL 5.1 is also installed on my system. i have searched the complete dir. but i am unable to find .


..\Application.h:32:28: mysql++/mysql++.h: No such file or directory
Build error occurred, build is stopped

I searched the complete directory but unable to locate the file...

Can any one help me please...

Posted On: Sunday 21st of October 2012 10:46:36 PM Total Views:  179
View Complete with Replies




Related Messages:

Mysql restarts ALOT (error included)   (276 Views)
, I have a heavy-traffic website and running 2 servers, one for apache and the other is for mysql .. both are celeron 2.6 with 1gb RAM, the mysql service restarts every 2 minutes by itself and here's what's written in the error messages .. Code: 061225 16:03:28 mysqld restarted 061225 16:03:29 InnoDB: Started; log sequence number 0 89760 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.13-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.13 061225 16:05:22 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed 16391 bytes) 061225 16:05:22 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed 16391 bytes) 061225 16:05:22 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed 16391 bytes) 061225 16:05:22 [ERROR] /usr/local/libexec/mysqld: Out of memory (Needed 16391 bytes) mysqld got signal 10; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=1044480 max_used_connections=83 max_connections=250 threads_connected=23 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 904214 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 061225 16:06:24 mysqld restarted 061225 16:06:24 InnoDB: Started; log sequence number 0 89760 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.13-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.13 mysqld got signal 10; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=1044480 max_used_connections=110 max_connections=250 threads_connected=24 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 904214 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 061225 16:10:16 mysqld restarted 061225 16:10:16 InnoDB: Started; log sequence number 0 89760 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.13-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.13 mysqld got signal 10; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=1044480 max_used_connections=105 max_connections=250 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 904214 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 061225 16:12:41 mysqld restarted 061225 16:12:41 InnoDB: Started; log sequence number 0 89760 /usr/local/libexec/mysqld: ready for connections. Version: '4.1.13-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-4.1.13 I tried to do "repair" for all the tables and still it restarts, any help will be greatly appretiated ..
dbconnect include file : where is the best place   (173 Views)
Is it best to have the php file that contains all of your dbconnect information in the directory before your htdocs (public_html etc) directory. I had a copy there that I linking to useing ../connectfile.php but some of my connections didn't work and I put it in the main htdocs and it seemed to fix the problem. But is it a security issue People shouldn't be able to see the info inside because it is php so all they would see is what is echoed to display in a webpage. Did I make sence