Javanian, Seun this thread is quite irrelevant now, kindly delete

DanielTheGeek:

Also coding at the moment and BTW, is anyone familiar with PostgreSql? I have some questions...

This postgresSql, I have never used it in production yet, I have however used it offline before, but not to any great extent.

Yeah it actually makes sense in production because if you're familiar with the Mysql "slave -> master replication" way of scaling apps then PostgreSql will appeal... It does this easily and faster.

But my issue is with the casting of MySql syntax to a PostgreSql one as my project started out with MySql and now I want to switch. I have an auto switching mechanism with a user interface that allows me switch databases with ease however it doesn't seem to work with PostgreSql. The tables get created in the PostgreSql database but the data doesn't get inserted. I'm thinking the insert statement isn't being casted. How do you write you regular OOP PostgreSql insert queries?

dhtml81:

This postgresSql, I have never used it in production yet, I have however used it offline before, but not to any great extent.

Hmn, i cannot remember the OOP PostgresSql. I normally use WRAPPERS to work, that way, I dont have to start cramming stuffs like that.

PDO right? That's why I'm stuck....all the examples I see online are either functional or use PDO.. I'd just use ClearDB for now.

dhtml81:
Hmn, i cannot remember the OOP PostgresSql. I normally use WRAPPERS to work, that way, I dont have to start cramming stuffs like that.

Last time I worked on a really huge website with heavy traffic. I used AWS, there is this stuff on amazon, i cannot remember the name now.
But it is a technique of creating some kind of read-only database. So the stuff splits your database into 2 - one read/write, the other read-only.

So queries that do you need to write can go to the read-only database, while the read/write ones go to the other database (the contents of both database are synchronized). And that was what solved the issue using MySQL.

Yeah in general terms, that's known as Slave -> master replication... Amazon just has a way of making things sound more complex than they really are. The thing is many developers don't even know about this technique yet they want to build a website that'll house a million members....

dhtml81:
Last time I worked on a really huge website with heavy traffic. I used AWS, there is this stuff on amazon, i cannot remember the name now.
But it is a technique of creating some kind of read-only database. So the stuff splits your database into 2 - one read/write, the other read-only.

So queries that do you need to write can go to the read-only database, while the read/write ones go to the other database (the contents of both database are synchronized). And that was what solved the issue using MySQL.

You can also imagine a developer telling me the only way to retrieve data from a database located on another server is to use MySql remote connection when we are in the era of web services (REST/SOAP)

mynd44 please what is going on?