feat: basic Go SQL driver implementation

[murfffi]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @murfffi, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes the initial implementation of a Go SQL driver designed to interact with Airtable. The primary goal is to enable Go applications to query and manipulate Airtable data using familiar SQL syntax and the standard database/sql interface. This foundational work includes the core driver logic, an integration test to confirm basic functionality, and a mechanism for automatic driver registration, paving the way for seamless Airtable integration within Go projects.

Highlights

• Core Go SQL Driver Implementation: Introduced the fundamental Go SQL driver for Airtable in driver.go, allowing applications to connect to Airtable using a DSN that includes an API key. This file contains the CreateDriver function and the logic for resolving the DSN to create an Airtable client.
• Integration Testing: Added driver_integ_test.go which includes an integration test to validate the basic functionality of the new driver. This test connects to Airtable using an environment variable for the API key and performs a simple SELECT query to ensure data retrieval works as expected.
• Automatic Driver Registration: A new register/register.go file was added with an init() function that automatically registers the Airtable SQL driver with Go's standard database/sql package. This simplifies usage, as developers only need to import the package to make the driver available.
• Interface Assertion Refactoring: Refactored the placement of interface assertions for sql.Database, sql.RowIter, sql.Disposable, and sql.Table across provider/airdb.go and provider/airsqltable.go for better organization and clarity.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a basic Go SQL driver for Airtable. The implementation includes the driver itself, a registration package for automatic setup, and an integration test. The code is well-structured and provides a good foundation. I've added a couple of suggestions to improve code clarity and test robustness. Specifically, I recommended refining a function signature to be more idiomatic and making the integration test skippable when required credentials are not available.