Question 1

How do I handle nullable parameters in Facil?

Accepted Answer

Facil treats stored procedure parameters with null defaults as nullable, wrapping them in Option or ValueOption. For scripts, you must specify nullability in the YAML config due to type inference limitations, as explained in the FAQ.

Question 2

Facil vs FSharp.Data.SqlClient: which is better for F# SQL access?

Accepted Answer

Facil generates plain F# code you check in, avoiding type provider performance issues and improving CI/CD compatibility, while FSharp.Data.SqlClient offers real-time updates but can cause IDE slowdowns, per the README's comparison.

Question 3

How to set up Facil for bulk inserts with temp tables?

Accepted Answer

Configure temp tables in the YAML file with SQL definitions or file paths, then use the generated API with SqlBulkCopy configuration for efficient data loading, as detailed in the temp tables section of the README.

Question 4

Can Facil work with Azure SQL databases?

Accepted Answer

Yes, as long as it's SQL Server 2012 or later, including Azure SQL, but ensure the connection string is accessible at build-time, as noted in the requirements.

Question 5

What's the best way to force regeneration in Facil?

Accepted Answer

Delete the first line of the generated file or set the FACIL_FORCE_REGENERATE environment variable; for CI, use FACIL_FAIL_ON_REGENERATE to ensure code is up-to-date, based on the FAQ.

Question 6

How does Facil handle dynamic SQL with changing result sets?

Accepted Answer

Facil executes dynamic SQL at build-time with sample parameters to infer columns, but for parameters affecting column names, use buildValue in the config to specify values, as warned in the README.

Facil

What is Facil?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions