Remove Index.php From URL CodeIgniter

Create the .htaccess file add the code given below and put it into your root directory of the main folder

And please keep this variable $config[‘index_page’] = ‘ ‘;  empty you can find this in config.php in config folder

RewriteEngine On
#Checks to see if the user is attempting to access a valid file,
#such as an image or css document, if this isn't true it sends the
#request to index.php
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
#This last condition enables access to the images and css folders, and the robots.txt file
RewriteCond $1 !^(index\.php|public|images|robots\.txt|css)
RewriteRule ^(.*)$ index.php/$1 [L]

Advertisements

Difference Between InnoDB and MyISAM

Difference between InnoDB and MyIsam

InnoDB MyISAM
Default engine from version 5.5 Default engine before version 5.5
ACID* Complaint (Atomicity, Consistency, Isolation, Durability)) Not ACID Complaint
Transactional (Rollback, Commit) Non-Transactional
Row Level Locking Table level Locking
Row data stored in pages as per primary keyorders No Particular order for data stored
Support foreign key Does not support relationship constraint
No full-text search Full-text search

Codeigniter Light Weight Framework

CodeIgniter Rocks

CodeIgniter is a powerful PHP framework with a very small footprint, built for developers who need a simple and elegant toolkit to create full-featured web applications.

Read User Guide Here

Notes

What’s inside the User Guide?

The User Guide contains an introduction, tutorial, a number of “how to” guides, and then reference documentation for the components that make up the framework.

Where else can I find the User Guide?

The user guide download is simply the zipped folder from the released version. It is included in the framework download.

Download User guide Here

Moving from MySQL to PostgreSQL

Moving from MySQL to PostgreSQL

Some Differences Between PostgreSQL + MySQL

In general, PostgreSQL makes a strong effort to conform to existing database standards, where MySQL has a mixed background on this. If you're coming from a background using MySQL or Microsoft Access, some of the changes can seem strange (such as not using double quotes to quote string values).

  • MySQL uses nonstandard '#' to begin a comment line; PostgreSQL doesn't. Instead, use '–' (double dash), as this is the ANSI standard, and both databases understand it.
  • MySQL uses ' or " to quote values (i.e. WHERE name = "John"). This is not the ANSI standard for databases. PostgreSQL uses only single quotes for this (i.e. WHERE name = 'John'). Double quotes are used to quote system identifiers; field names, table names, etc. (i.e. WHERE "last name" = 'Smith').
  • MySQL uses ` (accent mark or backtick) to quote system identifiers, which is decidedly non-standard.
  • PostgreSQL is case-sensitive for string comparisons. The field "Smith" is not the same as the field "smith". This is a big change for many users from MySQL and other small database systems, like Microsoft Access. In PostgreSQL, you can either:
    • Use the correct case in your query. (i.e. WHERE lname='Smith')
    • Use a conversion function, like lower() to search. (i.e. WHERE lower(lname)='smith')
    • Use a case-insensitive operator, like ILIKE or ~*
  • Database, table, field and columns names in PostgreSQL are case-independent, unless you created them with double-quotes around their name, in which case they are case-sensitive. In MySQL, table names can be case-sensitive or not, depending on which operating system you are using.
  • PostgreSQL and MySQL seem to differ most in handling of dates, and the names of functions that handle dates.
  • MySQL uses C-language operators for logic (i.e. 'foo' || 'bar' means 'foo' OR 'bar', 'foo' && 'bar' means 'foo' and 'bar'). This might be marginally helpful for C programmers, but violates database standards and rules in a significant way. PostgreSQL, following the standard, uses || for string concatenation ('foo' || 'bar' = 'foobar').
  • There are other differences between the two, such as the names of functions for finding the current user. MySQL has a tool, Crash-Me, which can useful for digging this out. (Ostensibly, Crash-Me is a comparison tool for databases; however, it tends to seriously downplay MySQL's deficiencies, and isn't very objective in what it lists: the entire idea of having procedural languages (a very important feature for many users!) is relegated to a single line on the bottom fifth of the document, while the fact that MySQL allows you to use || for logical-or (definitely non-standard), is listed way before this, as a feature. Be careful about its interpretations.)

Read more

https://wiki.postgresql.org/wiki/Things_to_find_out_about_when_moving_from_MySQL_to_PostgreSQL

CodeIgniter Rocks

CodeIgniter Rocks
CodeIgniter is a powerful PHP framework with a very small footprint, built for developers who need a simple and elegant toolkit to create full-featured web applications.

Why CodeIgniter?

 

Framework with a small footprint

CodeIgniter 3 has a 2MB download, including the user guide.

Clear documentation

The CodeIgniter User Guide comes with the download. It contains an introduction, tutorial, a number of “how to” guides, and then reference documentation for the components that make up the framework.

Compatibility with standard hosting

CodeIgniter 3 only needs PHP 5.3.7, and plays nicely with almost all shared or dedicated hosting platforms. Many webapps need a database, and CodeIgniter supports the most common, including MySQL.

No restrictive coding rules

Use your own coding and naming conventions, with only a few caveats that deal with classname conflicts. CodeIgniter looks to empower you, not shackle you.

Simple solutions over complexity

CodeIgniter encourages MVC, but does not force it on you.

Exceptional performance

CodeIgniter consistently outperforms most of its competitors.

No large-scale monolithic libraries

CodeIgniter is not trying to be all things to all people. It is a lean MVC framework, with enough capabilities to improve your productivity, while providing for third-party addons/plugins for additional functionality.

Nearly zero configuration

Much of the CodeIgniter configuration is done by convention, for instance putting models in a “models” folder. There are still a number of configuration options available, through scripts in the “config” folder.

No need for template language

CodeIgniter comes with a simple, substitution based, templating tool. Addons/plugins are available for most of the full-blown templating engines, if that is what you are used to.

Spend more time away from the computer

Don’t we all want it? CodeIgniter is easy to learn and to get proficient with.

PHP 7

PHP 7Are you looking for the latest status, news, articles, features or updates about the newest version after PHP 5.X? After a long voting process by the community, the name for the next major PHP version has been finalized! The winning proposal is to call the latest major version PHP 7.
So here’s the top 5 things you must know about PHP 7!
1:  THE LATEST PHP VERSION WILL BE RELEASED LATER THIS YEAR

The PHP 7 Timeline RFC was approved in a near unanimous vote, and aims to release PHP 7 in October 2015. Even if it’s delayed a bit, we’re still likely to see it before the year is out!! The final feature set for PHP 7 is almost completely finalized, and will officially close by the end of March.
See the PHP 7 timeline

2 : PHP SPACE SHIPS

080326-lynx-flying-02

PHP 7 will introduce a new operator <=> conveniently similar to a TIE fighter and dubbed the Spaceship Operator. It can be used for combined comparisons – mostly when dealing with sorting.
See more info

3: DECLARATIONS & SCALER TYPE HINTS

php7-scalar-type-hints-return-types-8-638

PHP 7 will allow developers to declare what kind of return type a function is expected to have – similar to argument Type Hints.

In addition, argument type hints and the new return-type declarations now support new scalar types, allowing developers to denote that they’re expecting strings, floats, ints or bools to be passed or returned.

4: PHP 7 PERFORMANCE

performance

PHP 7 is based on the PHPNG project (PHP Next-Gen), that was led by Zend to speed up PHP applications. The performance gains realized from PHP 7 are huge! They vary between 25% and 70% on real-world apps, and all of that just from upgrading PHP, without having to change a single line of code!

5: PHP 7 IS 2X FASTER

A6-faster

Since PHPNG was open sourced and later merged into PHP 7, its performance more than doubled in many cases, and we’re continuing to improve it all the time.

To put things in perspective – when PHPNG was published, the WordPress homepage required approx. 9.4 billion CPU instructions to execute.  As of now – it requires only 2.6 billion – that’s 72% less!

Blog at WordPress.com.

Up ↑

%d bloggers like this: