3 ms·
While the comment that many PHP applications depend on a MySQL database (I'd seriously expect WP to have some sort of DAL by now) is true it wouldn't be impossi
by RossM 18y ago
While the comment that many PHP applications depend on a MySQL database (I'd seriously expect WP to have some sort of DAL by now) is true it wouldn't be impossible for someone to write an extension to support Google's BigTable.
Article was a little confusing(ly structured) but surprised me by not completely bashing PHP.
I haven't actually used GAE and assume BigTable is another database platform.
- anamax 18y ago> I haven't actually used GAE and assume BigTable is another database platform. Background: GAE doesn't provide access to BigTable. It provides access to GAE Datastore which is built on top of BigTable. Both are key-value stores. I don't know how much indexing that bigtable provides, but datastore has a fair amount (under user control). There are no joins or aggregations in the GAE query API and queries can only return one type of object. (The provided subclass/roll-up model seems a little odd.) These constraints seem baked-in. The transaction model is basically "all objects under a given root name can be updated/created/deleted as an atomic operation." (Within said atomic operation, a given object can only be written once and I forget whether reads see writes.) This makes it hard to do certain sorts of real-world transactions. (Imagine transferring money between two accounts.) The datastore also has certain size and "number of object" limits. Then again, the platform limits the amount of time that each operation is allowed to take.