Update links to reflect repository move to sqlparser-rs GitHub org

CHANGELOG.md

@@ -6,7 +6,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 Given that the parser produces a typed AST, any changes to the AST will technically be breaking and thus will result in a `0.(N+1)` version. We document changes that break via addition as "Added".
 
 ## [Unreleased]
-Check https://github.com/ballista-compute/sqlparser-rs/commits/main for undocumented changes.
+Check https://github.com/sqlparser-rs/sqlparser-rs/commits/main for undocumented changes.
 
 
 ## [0.9.0] 2020-03-21

Cargo.toml

@@ -3,10 +3,10 @@ name = "sqlparser"
 description = "Extensible SQL Lexer and Parser with support for ANSI SQL:2011"
 version = "0.9.1-alpha.0"
 authors = ["Andy Grove <andygrove73@gmail.com>"]
-homepage = "https://github.com/ballista-compute/sqlparser-rs"
+homepage = "https://github.com/sqlparser-rs/sqlparser-rs"
 documentation = "https://docs.rs/sqlparser/"
 keywords = [ "ansi", "sql", "lexer", "parser" ]
-repository = "https://github.com/ballista-compute/sqlparser-rs"
+repository = "https://github.com/sqlparser-rs/sqlparser-rs"
 license = "Apache-2.0"
 include = [
     "src/**/*.rs",

README.md

@@ -2,7 +2,7 @@
 
 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 [![Version](https://img.shields.io/crates/v/sqlparser.svg)](https://crates.io/crates/sqlparser)
-[![Build Status](https://github.com/ballista-compute/sqlparser-rs/workflows/Rust/badge.svg?branch=main)](https://github.com/ballista-compute/sqlparser-rs/actions?query=workflow%3ARust+branch%3Amain)
+[![Build Status](https://github.com/sqlparser-rs/sqlparser-rs/workflows/Rust/badge.svg?branch=main)](https://github.com/sqlparser-rs/sqlparser-rs/actions?query=workflow%3ARust+branch%3Amain)
 [![Coverage Status](https://coveralls.io/repos/github/ballista-compute/sqlparser-rs/badge.svg?branch=main)](https://coveralls.io/github/ballista-compute/sqlparser-rs?branch=main)
 [![Gitter Chat](https://badges.gitter.im/sqlparser-rs/community.svg)](https://gitter.im/sqlparser-rs/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
@@ -123,10 +123,10 @@ resources.
 
 [tdop-tutorial]: https://eli.thegreenplace.net/2010/01/02/top-down-operator-precedence-parsing
 [`cargo fmt`]: https://github.com/rust-lang/rustfmt#on-the-stable-toolchain
-[current issues]: https://github.com/ballista-compute/sqlparser-rs/issues
+[current issues]: https://github.com/sqlparser-rs/sqlparser-rs/issues
 [DataFusion]: https://github.com/apache/arrow-datafusion
 [LocustDB]: https://github.com/cswinter/LocustDB
-[Ballista]: https://github.com/ballista-compute/ballista
+[Ballista]: https://github.com/apache/arrow-datafusion/tree/master/ballista
 [Pratt Parser]: https://tdop.github.io/
 [sql-2016-grammar]: https://jakewheat.github.io/sql-overview/sql-2016-foundation-grammar.html
 [sql-standard]: https://en.wikipedia.org/wiki/ISO/IEC_9075

docs/releasing.md

@@ -2,7 +2,7 @@
 
 ## Prerequisites
 Publishing to crates.io has been automated via GitHub Actions, so you will only
-need push access to the [ballista-compute GitHub repository](https://github.com/ballista-compute/sqlparser-rs)
+need push access to the [sqlparser-rs GitHub repository](https://github.com/sqlparser-rs/sqlparser-rs)
 in order to publish a release.
 
 We use the [`cargo release`](https://github.com/sunng87/cargo-release)
@@ -41,7 +41,7 @@ $ cargo install cargo-release
     * Create a new tag (e.g. `v0.8.0`) locally
     * Push the new tag to the specified remote (`upstream` in the above
       example), which will trigger a publishing process to crates.io as part of
-      the [corresponding GitHub Action](https://github.com/ballista-compute/sqlparser-rs/blob/main/.github/workflows/rust.yml).
+      the [corresponding GitHub Action](https://github.com/sqlparser-rs/sqlparser-rs/blob/main/.github/workflows/rust.yml).
 
       Note that credentials for authoring in this way are securely stored in
       the (GitHub) repo secrets as `CRATE_TOKEN`.

tests/sqlparser_common.rs

@@ -3295,7 +3295,7 @@ fn parse_start_transaction() {
     verified_stmt("START TRANSACTION ISOLATION LEVEL REPEATABLE READ");
     verified_stmt("START TRANSACTION ISOLATION LEVEL SERIALIZABLE");
 
-    // Regression test for https://github.com/ballista-compute/sqlparser-rs/pull/139,
+    // Regression test for https://github.com/sqlparser-rs/sqlparser-rs/pull/139,
     // in which START TRANSACTION would fail to parse if followed by a statement
     // terminator.
     assert_eq!(

tests/sqlparser_postgres.rs

@@ -233,7 +233,7 @@ fn parse_create_table_with_inherit() {
 #[test]
 fn parse_create_table_empty() {
     // Zero-column tables are weird, but supported by at least PostgreSQL.
-    // <https://github.com/ballista-compute/sqlparser-rs/pull/94>
+    // <https://github.com/sqlparser-rs/sqlparser-rs/pull/94>
     let _ = pg_and_generic().verified_stmt("CREATE TABLE t ()");
 }