sapling/tests/test-hgsql-filenames.t

#testcases case-innodb case-rocksdb

#if case-rocksdb
  $ DBENGINE=rocksdb
#else
  $ DBENGINE=innodb
#endif

  $ . "$TESTDIR/hgsql/library.sh"

# Populate the db with an initial commit

  $ initclient client
  $ cd client
  $ echo x > x
  $ hg commit -qAm x
  $ cd ..

  $ initserver master masterrepo
  $ cd master
  $ hg log
  $ hg pull -q ../client

# Verify committing odd filenames works (with % character)

  $ hg up
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  $ echo a > 'bad%name'
  $ hg commit -Am badname
  adding bad%name
  $ echo b > 'bad%name'
  $ hg commit -Am badname2
Add support for RocksDB Summary: - Add support for RocksDB engine (developed as a drop in replacement for innodb) to hgsql to allow new xdb.hgsql.1-10 shards to host hg repos - Prefer MySQL test DBs in same region - Run all hgsql unit tests also for RocksDB engine - Allow for nested ifs to make that possible (downside if you switch off rockdb tests, innodb tests are run twice) Reviewed By: quark-zju Differential Revision: D7014064 fbshipit-source-id: 073c36176aa7eaf74252ef33c3f47da594920b28 2018-02-21 16:55:07 +03:00			`#testcases case-innodb case-rocksdb`

			`#if case-rocksdb`
			`$ DBENGINE=rocksdb`
			`#else`
			`$ DBENGINE=innodb`
			`#endif`

hgsql: integrate with hg-crew Summary: Move hgsql into the hgext directory, and the tests to tests/test-hgsql-*. Update the tests to refer to the new places for things. Test Plan: Run the hgsql tests and make sure they pass. Reviewers: #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D6660499 Tasks: T24908724 2018-01-04 18:22:19 +03:00			`$ . "$TESTDIR/hgsql/library.sh"`
Change expected rev validation to use the builtin sql escaping Previously we escaped path names ourselves, but this didn't remove %'s from the paths, which could break the sql libraries ability to format queries with args. Now we use the actual sql libraries builtin formatting. 2014-04-17 21:33:37 +04:00
			`# Populate the db with an initial commit`

			`$ initclient client`
			`$ cd client`
			`$ echo x > x`
			`$ hg commit -qAm x`
			`$ cd ..`

			`$ initserver master masterrepo`
			`$ cd master`
			`$ hg log`
			`$ hg pull -q ../client`

Hide unnecessary sql warning Commit 70d94df78f11 tried to hide this benign warning, but did it at the wrong spot. This does it at the right spot (around cursor.close()). This is the description from the original commit: The revision_references table has multiple unique keys (primary key, and a unique name index). Using ON DUPLICATE KEY in an INSERT causes a warning, since it will only update one of the rows, even if there are two duplicates. We can safely ignore this since we know there will only ever be one row that has a duplicate key. 2014-04-17 22:09:48 +04:00			`# Verify committing odd filenames works (with % character)`
Change expected rev validation to use the builtin sql escaping Previously we escaped path names ourselves, but this didn't remove %'s from the paths, which could break the sql libraries ability to format queries with args. Now we use the actual sql libraries builtin formatting. 2014-04-17 21:33:37 +04:00
			`$ hg up`
			`1 files updated, 0 files merged, 0 files removed, 0 files unresolved`
			`$ echo a > 'bad%name'`
			`$ hg commit -Am badname`
			`adding bad%name`
			`$ echo b > 'bad%name'`
			`$ hg commit -Am badname2`