As of Jan 2017 the sqlite3 limits page defines the practical limits to this question based on the maximum size of the database which is 140 terabytes: Maximum Number Of Rows In A Table The theoretical maximum number of rows in a table is 2^64 (18446744073709551616 or about 1.8e+19). This limit is unreachable since the … Read more
regular 4 byte INT is way too big, is a waste of space! You don’t say what database you’re using, so I can’t recommend a specific datatype. Everyone is saying “use integer”, but most databases store integers as 4 bytes, which is way more than you need. You should use a two byte integer (smallint … Read more
Write locally to disk, then batch insert to the database periodically (e.g. at log rollover time). Do that in a separate, low-priority process. More efficient and more robust… (Make sure that your database log table contains a column for “which machine the log event came from” by the way – very handy!)
This is how you do it: heroku pg:psql –app YOUR_APP_NAME_HERE < updates.sql And if you want to restore your production into staging (assuming both are heroku postgres DBs): heroku pgbackups:restore YOUR_STAGING_DATABASE_NAME `heroku pgbackups:url –app YOUR_PRODUCTION_APP_NAME` –app YOUR_STAGING_APP_NAME –confirm YOUR_STAGING_APP_NAME Make sure to preserve the special single quotes around heroku pgbackups:url –app YOUR_PRODUCTION_APP_NAME. HEROKU TOOLBELT UPDATE … Read more
Usually in project build.gradle I define the dependencies versions: ext { buildToolsVersion = ‘25.0.2’ supportLibVersion = ‘25.3.1’ espressoVersion = ‘2.2.2’ archRoomVersion = ‘1.0.0-alpha1’ } so in app build.gradle the dependencies look like: dependencies { compile fileTree(dir: ‘libs’, include: [‘*.jar’]) compile “org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version” compile “com.android.support:appcompat-v7:${rootProject.supportLibVersion}” compile “android.arch.persistence.room:runtime:${rootProject.archRoomVersion}” annotationProcessor “android.arch.persistence.room:compiler:${rootProject.archRoomVersion}” kapt “android.arch.persistence.room:compiler:${rootProject.archRoomVersion}” androidTestCompile(“com.android.support.test.espresso:espresso-core:${rootProject.espressoVersion}”, { exclude group: ‘com.android.support’, module: … Read more
The problem is that your application probably still holds some connection to the database (or another application holds connection as well). Database cannot be deleted where there is any other opened connection. The first problem can be probably solved by turning connection pooling off (add Pooling=false to your connection string) or clear the pool before … Read more
Mythology I always thought that databases should be denormalized for reading, as it is done for OLAP database design, and not exaggerated much further 3NF for OLTP design. There’s a myth to that effect. In the Relational Database context, I have re-implemented six very large so-called “de-normalised” “databases”; and executed over eighty assignments correcting problems … Read more
Assuming by full dump you also mean the VIEWs and the EVENTs, you would need: GRANT USAGE ON *.* TO ‘dump’@’%’ IDENTIFIED BY …; GRANT SELECT, LOCK TABLES ON `mysql`.* TO ‘dump’@’%’; GRANT SELECT, LOCK TABLES, SHOW VIEW, EVENT, TRIGGER ON `myschema`.* TO ‘dump’@’%’; and if you have VIEWs that execute a function, then unfortunately … Read more
gender.c is an open source C program that does a good job. It comes with data for 44568 first names from all around the world. There is good documentation and a description of the file format (basically plain text) so it should not be to difficult to read it from your own application. Here is … Read more
I have a few fairly simple rules of thumb I follow when designing databases, which I think can be used to help make decisions like this…. Favor normalization. Denormalization is a form of optimization, with all the requisite tradeoffs, and as such it should be approached with a YAGNI attitude. Make sure that client code … Read more