meta user
network profile
| bio | website | starshine.org/jimd |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 1 month |
| seen | Apr 23 at 8:16 | |
| stats | profile views | 2 |
|
Jun 26 |
awarded | Scholar |
|
Jun 26 |
accepted | Using an older MySQL binlog filename (with position zero)? Risks? Downsides? |
|
May 17 |
awarded | Student |
|
May 17 |
asked | Using an older MySQL binlog filename (with position zero)? Risks? Downsides? |
|
Apr 14 |
awarded | Supporter |
|
Apr 13 |
awarded | Teacher |
|
Apr 13 |
answered | Is a Junction Table the same as a Weak Entity? |
|
Apr 9 |
answered | Which database engines will allow me to GRANT/REVOKE on a specific column? |
|
Mar 31 |
comment |
What are the differences between NoSQL and a traditional RDBMS? The important note here is that eschewing relations (foreign key) support in the database/server infrastructure relieves the database/servers from the load and lock-management overhead of maintaining referential integrity. The consequence of this, the trade-off, is that referential integrity, consistency, and the other ACID concerns are then pushed out to the applications. Many applications benefit from this rather than being limited by it. (Some applications have to be wedged into the client/server model). |
|
Mar 29 |
comment |
Is REINDEX dangerous? I'm thinking I was mistaken about it being row level security. Further reading suggests that it's more about the MVCC "visibility" (are some of those rows still locked in transactions which have yet to be committed). |
|
Mar 29 |
answered | Is REINDEX dangerous? |
|
Mar 29 |
comment |
Is REINDEX dangerous? I read somewhere that COUNT(*) performance issues in PostgreSQL can be caused by the need for the server to check the permissions on every tuple during the table scan (to determine which rows are visible to the entity performing the query). |
