If you simply run:
git add -u
git will update its index to know that the files that you’ve deleted should actually be part of the next commit. Then you can run “git commit” ( eg: git commit -m “Deleted files manually”) to check in that change.
Or, if you run:
git commit -a
It will automatically take these changes (and any others) and commit them.
First check if your command line recognizes mysql command. If not go to command and type in
set path=c:\wamp\bin\mysql\mysql5.1.17\bin
Then use this command to export your database
mysqldump -u YourUserName -p YourDatabaseName > backup_database_file_name.sql
This exports the database to the path you are currently in, while executing this command
More commands fro export/Backup database or databases.
# Backup a single database
# NOTE: you can also use the shortcuts -u and -p to specify username and password
mysqldump –user=… –password=… your_database_name > your_database_name.sql# Backup multiple databases:
mysqldump –user=… –password=… –databases db1 db2 > backup.sql# or all the databases in one shot:
mysqldump –user=… –password=… –all-databases > backup.sql# Optionally, it’s easy to compress the backup, for example with gzip:
mysqldump –user=… –password=… your_database_name \
| gzip > your_database_name.sql# And, if your database also has other objects (apart from tables) such as functions,
# views, and stored procedures, you can back them up too with –routines:mysqldump –user=… –password=… –routines \
your_database_name > your_database_name.sql# It may also be useful to include a timestamp in the target file name, so to know
# right away when a backup was taken:mysqldump –user=… –password=… \
your_database_name > “your_database_name-$(date +%Y-%m-%d-%H.%M.%S).sql”# If you are backing up data with the purpose of restoring it to an instance you want
# to use as replication slave, then the option –master-data is handy as it adds to
# the dump the information needed to configure the connection with the
# replication master:mysqldump –user=… –password=… –all-databases –master-data > backup.sql
CODEIGNITER ROCKS
Every once and a while you come across a blog post or forum discussion about what PHP application framework is the best. They each have their own positives and negatives, but the true answer to that question is that it depends on the programmer. Each programmer has a different style and different priorities when it comes to adopting a tool kit to use when building apps.
My framework of choice is CodeIgniter (CI) and below are my 10 reasons why CI rocks:
9. MVC Architecture
The model, view, controller architecture is nothing new. It seems like all the coding frameworks are MVC nowadays, and if they aren’t it can be configured easily. I have had experience building large apps the procedural way and every time they end up with unmanageable spaghetti code. The MVC way of doing things offers nice code separation and keeps things clean. Some frameworks force you…
View original post 684 more words
WordPress Developer Kerala India 