initial commit

Author: rustyconover

.github/workflows/MainDistributionPipeline.yml

@@ -20,21 +20,21 @@ jobs:
     with:
       duckdb_version: main
       ci_tools_version: main
-      extension_name: quack
+      extension_name: textplot
 
   duckdb-stable-build:
     name: Build extension binaries
     uses: duckdb/extension-ci-tools/.github/workflows/_extension_distribution.yml@v1.3.2
     with:
       duckdb_version: v1.3.2
       ci_tools_version: v1.3.2
-      extension_name: quack
+      extension_name: textplot
 
   code-quality-check:
     name: Code Quality Check
     uses: duckdb/extension-ci-tools/.github/workflows/_extension_code_quality.yml@main
     with:
       duckdb_version: v1.3.2
       ci_tools_version: main
-      extension_name: quack
+      extension_name: textplot
       format_checks: 'format;tidy'

CMakeLists.txt

@@ -1,27 +1,29 @@
 cmake_minimum_required(VERSION 3.5)
 
 # Set extension name here
-set(TARGET_NAME quack)
+set(TARGET_NAME textplot)
+
+set(CMAKE_CXX_STANDARD 17)
+set(CMAKE_CXX_STANDARD_REQUIRED ON)
 
 # DuckDB's extension distribution supports vcpkg. As such, dependencies can be added in ./vcpkg.json and then
 # used in cmake with find_package. Feel free to remove or replace with other dependencies.
 # Note that it should also be removed from vcpkg.json to prevent needlessly installing it..
-find_package(OpenSSL REQUIRED)
 
 set(EXTENSION_NAME ${TARGET_NAME}_extension)
 set(LOADABLE_EXTENSION_NAME ${TARGET_NAME}_loadable_extension)
 
 project(${TARGET_NAME})
 include_directories(src/include)
 
-set(EXTENSION_SOURCES src/quack_extension.cpp)
+set(EXTENSION_SOURCES src/textplot_extension.cpp)
 
 build_static_extension(${TARGET_NAME} ${EXTENSION_SOURCES})
 build_loadable_extension(${TARGET_NAME} " " ${EXTENSION_SOURCES})
 
 # Link OpenSSL in both the static library as the loadable extension
-target_link_libraries(${EXTENSION_NAME} OpenSSL::SSL OpenSSL::Crypto)
-target_link_libraries(${LOADABLE_EXTENSION_NAME} OpenSSL::SSL OpenSSL::Crypto)
+target_link_libraries(${EXTENSION_NAME})
+target_link_libraries(${LOADABLE_EXTENSION_NAME})
 
 install(
   TARGETS ${EXTENSION_NAME}

Makefile

@@ -1,7 +1,7 @@
 PROJ_DIR := $(dir $(abspath $(lastword $(MAKEFILE_LIST))))
 
 # Configuration of extension
-EXT_NAME=quack
+EXT_NAME=textplot
 EXT_CONFIG=${PROJ_DIR}extension_config.cmake
 
 # Include the Makefile from extension-ci-tools

docs/NEXT_README.md

@@ -1,10 +1,10 @@
-# Quack
+# Textplot
 
 This repository is based on https://github.com/duckdb/extension-template, check it out if you want to build and ship your own DuckDB extension.
 
 ---
 
-This extension, Quack, allow you to ... <extension_goal>.
+This extension, Textplot, allow you to ... <extension_goal>.
 
 
 ## Building
@@ -26,23 +26,23 @@ The main binaries that will be built are:
 ```sh
 ./build/release/duckdb
 ./build/release/test/unittest
-./build/release/extension/quack/quack.duckdb_extension
+./build/release/extension/textplot/textplot.duckdb_extension
 ```
 - `duckdb` is the binary for the duckdb shell with the extension code automatically loaded.
 - `unittest` is the test runner of duckdb. Again, the extension is already linked into the binary.
-- `quack.duckdb_extension` is the loadable binary as it would be distributed.
+- `textplot.duckdb_extension` is the loadable binary as it would be distributed.
 
 ## Running the extension
 To run the extension code, simply start the shell with `./build/release/duckdb`.
 
-Now we can use the features from the extension directly in DuckDB. The template contains a single scalar function `quack()` that takes a string arguments and returns a string:
+Now we can use the features from the extension directly in DuckDB. The template contains a single scalar function `textplot()` that takes a string arguments and returns a string:
 ```
-D select quack('Jane') as result;
+D select textplot('Jane') as result;
 ┌───────────────┐
 │    result     │
 │    varchar    │
 ├───────────────┤
-│ Quack Jane 🐥 │
+│ Textplot Jane 🐥 │
 └───────────────┘
 ```
 
@@ -81,6 +81,6 @@ DuckDB. To specify a specific version, you can pass the version instead.
 
 After running these steps, you can install and load your extension using the regular INSTALL/LOAD commands in DuckDB:
 ```sql
-INSTALL quack
-LOAD quack
+INSTALL textplot
+LOAD textplot
 ```

docs/README.md

@@ -2,7 +2,7 @@
 This repository contains a template for creating a DuckDB extension. The main goal of this template is to allow users to easily develop, test and distribute their own DuckDB extension. The main branch of the template is always based on the latest stable DuckDB allowing you to try out your extension right away.
 
 ## Getting started
-First step to getting started is to create your own repo from this template by clicking `Use this template`. Then clone your new repository using 
+First step to getting started is to create your own repo from this template by clicking `Use this template`. Then clone your new repository using
 ```sh
 git clone --recurse-submodules https://github.com/<you>/<your-new-extension-repo>.git
 ```
@@ -30,7 +30,7 @@ The main binaries that will be built are:
 ./build/release/test/unittest
 ./build/release/extension/<extension_name>/<extension_name>.duckdb_extension
 ```
-- `duckdb` is the binary for the duckdb shell with the extension code automatically loaded. 
+- `duckdb` is the binary for the duckdb shell with the extension code automatically loaded.
 - `unittest` is the test runner of duckdb. Again, the extension is already linked into the binary.
 - `<extension_name>.duckdb_extension` is the loadable binary as it would be distributed.
 
@@ -44,16 +44,16 @@ GEN=ninja make
 ```
 
 ## Running the extension
-To run the extension code, simply start the shell with `./build/release/duckdb`. This shell will have the extension pre-loaded.  
+To run the extension code, simply start the shell with `./build/release/duckdb`. This shell will have the extension pre-loaded.
 
-Now we can use the features from the extension directly in DuckDB. The template contains a single scalar function `quack()` that takes a string arguments and returns a string:
+Now we can use the features from the extension directly in DuckDB. The template contains a single scalar function `textplot()` that takes a string arguments and returns a string:
 ```
-D select quack('Jane') as result;
+D select textplot('Jane') as result;
 ┌───────────────┐
 │    result     │
 │    varchar    │
 ├───────────────┤
-│ Quack Jane 🐥 │
+│ Textplot Jane 🐥 │
 └───────────────┘
 ```
 
@@ -92,7 +92,7 @@ To distribute your extension binaries, there are a few options.
 The recommended way of distributing extensions is through the [community extensions repository](https://github.com/duckdb/community-extensions).
 This repository is designed specifically for extensions that are built using this extension template, meaning that as long as your extension can be
 built using the default CI in this template, submitting it to the community extensions is a very simple process. The process works similarly to popular
-package managers like homebrew and vcpkg, where a PR containing a descriptor file is submitted to the package manager repository. After the CI in the 
+package managers like homebrew and vcpkg, where a PR containing a descriptor file is submitted to the package manager repository. After the CI in the
 community extensions repository completes, the extension can be installed and loaded in DuckDB with:
 ```SQL
 INSTALL <my_extension> FROM community;
@@ -125,18 +125,18 @@ LOAD <my_extension>
 ```
 
 ### Versioning of your extension
-Extension binaries will only work for the specific DuckDB version they were built for. The version of DuckDB that is targeted 
-is set to the latest stable release for the main branch of the template so initially that is all you need. As new releases 
+Extension binaries will only work for the specific DuckDB version they were built for. The version of DuckDB that is targeted
+is set to the latest stable release for the main branch of the template so initially that is all you need. As new releases
 of DuckDB are published however, the extension repository will need to be updated. The template comes with a workflow set-up
 that will automatically build the binaries for all DuckDB target architectures that are available in the corresponding DuckDB
 version. This workflow is found in `.github/workflows/MainDistributionPipeline.yml`. It is up to the extension developer to keep
-this up to date with DuckDB. Note also that its possible to distribute binaries for multiple DuckDB versions in this workflow 
+this up to date with DuckDB. Note also that its possible to distribute binaries for multiple DuckDB versions in this workflow
 by simply duplicating the jobs.
 
-## Setting up CLion 
+## Setting up CLion
 
 ### Opening project
-Configuring CLion with the extension template requires a little work. Firstly, make sure that the DuckDB submodule is available. 
+Configuring CLion with the extension template requires a little work. Firstly, make sure that the DuckDB submodule is available.
 Then make sure to open `./duckdb/CMakeLists.txt` (so not the top level `CMakeLists.txt` file from this repo) as a project in CLion.
 Now to fix your project path go to `tools->CMake->Change Project Root`([docs](https://www.jetbrains.com/help/clion/change-project-root-directory.html)) to set the project root to the root dir of this repo.
 

extension_config.cmake

@@ -1,7 +1,7 @@
 # This file is included by DuckDB's build system. It specifies which extension to load
 
 # Extension from this repo
-duckdb_extension_load(quack
+duckdb_extension_load(textplot
     SOURCE_DIR ${CMAKE_CURRENT_LIST_DIR}
     LOAD_TESTS
 )

scripts/bootstrap-template.py

@@ -172,14 +172,14 @@ def replace_placeholders(file_name: str) -> None:
     files_to_search.extend(Path("./src").rglob("./**/*.txt"))
     files_to_search.extend(Path("./src").rglob("./*.md"))
 
-    replace_everywhere("quack", name_extension)
-    replace_everywhere("Quack", name_extension.capitalize())
+    replace_everywhere("textplot", name_extension)
+    replace_everywhere("Textplot", name_extension.capitalize())
     replace_everywhere("<extension_name>", name_extension)
 
     remove_placeholder()
 
     string_to_replace = name_extension
-    string_to_find = "quack"
+    string_to_find = "textplot"
 
     # rename files
     os.rename(f"test/sql/{string_to_find}.test", f"test/sql/{string_to_replace}.test")

src/include/quack_extension.hpp

@@ -1,11 +1,11 @@
 # Testing this extension
-This directory contains all the tests for this extension. The `sql` directory holds tests that are written as [SQLLogicTests](https://duckdb.org/dev/sqllogictest/intro.html). DuckDB aims to have most its tests in this format as SQL statements, so for the quack extension, this should probably be the goal too.
+This directory contains all the tests for this extension. The `sql` directory holds tests that are written as [SQLLogicTests](https://duckdb.org/dev/sqllogictest/intro.html). DuckDB aims to have most its tests in this format as SQL statements, so for the textplot extension, this should probably be the goal too.
 
 The root makefile contains targets to build and run all of these tests. To run the SQLLogicTests:
 ```bash
 make test
 ```
-or 
+or
 ```bash
 make test_debug
 ```