Azure / Azure/azure-functions-sql-extension

Allow schema renaming for internal state tables

Open
#1,053 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
130
Forks
71
Avg merge
4d 8h
Merged PRs (30d)
4

Description

**Problem**
We have a logic app with SQL trigger and a function with a SQL trigger running against the same database. Both use the internal state tables. The problem is that they seem to be having different requirements regarding the schema. The SQL trigger on the function adds a not nullable LastAccessTime column which is not used by the SQL trigger on the logic app, making it fail. We now manually changed the column to be nullable. However that's not something that you'd want to do.

**Solution**
A solution to this problem would be to allow for a configurable schema name on the SQL trigger for functions.

**Describe alternatives you've considered**
We mitigated the problem by making the LastAccessTime column nullable.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the SQL trigger creates and accesses its internal state tables, then compare the schema expectations of function and logic app triggers. Done means the function SQL trigger accepts a configurable schema name and avoids the conflicting LastAccessTime requirement described in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, sql
Domain
backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.