WHERE datefired ISNULL and seniorstaff = TRUE

SELECT staffid, firstname || lastname as fullname Is-not-fired and is-senior-staff, in PostgreSQL, I'd make a VIEW of all Would you want to, though? PostgreSQL has many features MySQL doesn't, like:įor instance, rather than coding in the web front end the logic of You can easily translate this to PostgreSQL. (this is generic pseudo-code, it would easily translate to PHP, Zope, With MySQL, you'd do something like this: You want to list every current senior staff member's name, some info about them, and a list of their goals. Imagine you're building a dynamic website for human resources. The important things (for me, at least) are more than just 'how do I do this MySQL thing in PostgreSQL?', but 'is there a much better way to think about this, which MySQL never even supported?' (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. MySQL has a tool, Crash-Me, which can useful for digging this out. There are other differences between the two, such as the names of functions for finding the current user.PostgreSQL, following the standard, uses || for string concatenation ('foo' || 'bar' = 'foobar'). This might be marginally helpful for C programmers, but violates database standards and rules in a significant way.

'foo' || 'bar' means 'foo' OR 'bar', 'foo' & 'bar' means 'foo' and 'bar').

MySQL uses C-language operators for logic (i.e.

PostgreSQL and MySQL seem to differ most in handling of dates, and the names of functions that handle dates.

In MySQL, table names can be case-sensitive or not, depending on which operating system you are using.

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.

Use a case-insensitive operator, like ILIKE or ~*.

Use a conversion function, like lower() to search.

This is a big change for many users from MySQL and other small database systems, like Microsoft Access. The field 'Smith' is not the same as the field 'smith'.

PostgreSQL is case-sensitive for string comparisons.

MySQL uses ` (accent mark or backtick) to quote system identifiers, which is decidedly non-standard.

Double quotes are used to quote system identifiers field names, table names, etc. PostgreSQL uses only single quotes for this (i.e. This is not the ANSI standard for databases.

MySQL uses ' or ' to quote values (i.e.

Instead, use '-' (double dash), as this is the ANSI standard, and both databases understand it.

MySQL uses nonstandard '#' to begin a comment line PostgreSQL doesn't.

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). In general, PostgreSQL makes a strong effort to conform to existing database standards, where MySQL has a mixed background on this. Some Differences Between PostgreSQL + MySQL

Relatively speedy and painless database that works great on practically every However, its support for many 'high-end' database features is scarce (to itsĬredit, in its place is an extremely easy-to-install, easy-to-administer, Universe, and might be scalable to counting the grains of sand on every beach. MySQL might be useful for the most complicated database project in the

Mysql like vs having