SQLDelight database class generating problem

Recently, I have been struggling with generating a database class for the SQLDelight schema and couldn't find a relevant answer to my problem. So this post might help someone who faces similar errors.

First, I had this nasty error while I tried to generate a class for the database schema with a Gradle task(generateSqlDelightInterface):

Unable to find method ''void kotlin.jvm.internal.FunctionReferenceImpl.<init>(int, java.lang.Class, java.lang.String, java.lang.String, int)'' 'void kotlin.jvm.internal.FunctionReferenceImpl.<init>(int, java.lang.Class, java.lang.String, java.lang.String, int)'

The solution was simple - upgrade Gradle Version to 6.8-milestone-2 in Project Structure/Project. It seems there was some bug in the older version.

Second, I had a problem with generating the actual class for the schema. This mechanism is pretty cranky to the directories configuration. You have to be watchful and put the schema file to the directory corresponding to the package which you specified in the build gradle file. 

Here is my working example:

build.gradle.file: 





"packageName" - must be with the same structure as the location of the schema file inside the sqldelight folder. 


"sourceFolders" - list of directories inside of commonMain to scan for a schema file. Note that here you specify only a root folder. Inside that root folder, the location of a schema must match the specified "packageName" structure.  



Comments

Post a Comment

Popular posts from this blog

The Operation Result Pattern in Java

Image
Introduction Throughout my career as a Java developer, I've frequently implemented a particular pattern across numerous projects. This pattern, known as the operation result pattern , encapsulates the outcome of an operation along with its return object, enhancing code clarity. It distinctly categorizes function call outcomes into success or failure, each requiring appropriate handling by the developer. In contrast, certain languages, such as Kotlin, integrate this pattern within their standard libraries, or like Golang, facilitate the return of additional information to indicate the operation's outcome. Unfortunately, Java lacks such a built-in solution, prompting the need for a standardized approach. Motivated by this gap, I created a library that implements the result pattern in the JResult , a library aimed at brining the operation result pattern in Java applications. Java's Built-in Error Handling Mechanisms Java's conventional approach to managing errors reli...
Read more

Bringing the Operation Result Pattern into Java

Image
Throughout my journey in various Java projects, I've consistently encountered the need to reimplement a specific pattern — one that encapsulates the results of operations without resorting to exceptions, such as during input validation.  This pattern, known as the Operation Result Pattern, may not be universally recognized as a formal design pattern, but in my experience, it's an incredibly useful approach for handling operation outcomes. I thought it would be nice to have it in a form of a simple library that can be easily integrated in the Java projects. After dedicating a few weeks to development, I'm excited to announce the release of the first version of this library, which I've named JResult.  It's designed to be lightweight, easy to use, and flexible enough to accommodate various project needs. You can explore JResult and its documentation on GitHub: https://github.com/ArtyomPanfutov/jresult Stay tuned for updates, and don't hesitate to contribute or reac...
Read more