How to resolve error 'ORA-00911: invalid character' in Golang?
During the Golang development process, we sometimes encounter errors such as "ORA-00911: invalid character". This error is usually caused by using invalid characters in the SQL statement. To solve this problem, we can take some simple methods. First of all, before executing the SQL statement, we should carefully check whether there are special characters or invalid characters in the statement. Secondly, we can try to use quotes to enclose fields or values that contain special characters to avoid errors. In addition, you can also use escape characters to process special characters to ensure that they are correctly recognized and processed in SQL statements. Through these methods, we can effectively solve the "ORA-00911: invalid character" problem in Golang and ensure that our program can run normally.
Question content
I encountered the error "ORA-00911: invalid character" when calling the following function. If I use a SQL query with hardcoded values (as of now, it's commented out in the snippet below), then I can get the database records in a JSON response in Postman without any issues. So, it looks like I'm doing my argument wrong. FYI, I am using "github.com/sijms/go-ora/v2" package to connect to oracle db. Also, the "DashboardRecordsRequest" structure is in the data model package, but I've pasted it into the snippet below for reference. Please note that when I do the POC we will be using stored procedures to interact with Oracle.
Postman request payload:
<code>{ "username": "UserABC", "startindex": 0, "pagesize": 10, "sortby": "requestnumber", "sortorder": "DESC" } </code>
Execution code:
<code>type DashboardRecordsRequest struct { Username string `json:"username"` StartIndex int `json:"startindex"` PageSize int `json:"pagesize"` SortBy string `json:"sortby"` SortOrder string `json:"sortorder"` } func GetDashboardActiveRequestRecords(request datamodel.DashboardRecordsRequest) ([]datamodel.ActiveRequestRecord, error) { sortby := request.SortBy sortorder := request.SortOrder startindex := request.StartIndex pagesize := request.PageSize activerecords := []datamodel.ActiveRequestRecord{} slog.Info("Verify values", slog.String("sortby", sortby), slog.String("sortorder", sortorder), slog.Int("startindex", startindex), slog.Int("pagesize", pagesize)) dbconn, err := getDBConnection() if err != nil { logger.Error("Could not connect to database") return activerecords, err } stmt, err := dbconn.Prepare("SELECT requestnumber, requeststatus, NVL(requestor, 'N/A'), NVL(pendingwith, 'N/A'), NVL(processtype, 'N/A'), actiondate FROM requests WHERE requeststatus = 'PENDINGAPPROVAL' ORDER BY ? ? OFFSET ? ROWS FETCH NEXT ? ROWS ONLY") /*stmt, err := dbconn.Prepare("SELECT requestnumber, requeststatus, NVL(requestor, 'N/A'), NVL(pendingwith, 'N/A'), NVL(processtype, 'N/A'), actiondate FROM requests WHERE requeststatus = 'PENDINGAPPROVAL' ORDER BY requestnumber DESC OFFSET 0 ROWS FETCH NEXT 10 ROWS ONLY")*/ if err != nil { logger.Error("Error while building prepared statement for retrieving dashboard active records", slog.String("Error", err.Error())) return activerecords, err } rows, err := stmt.Query(sortby, sortorder, startindex, pagesize) //rows, err := stmt.Query() if err != nil { logger.Error("Error while executing prepared statement for retrieving dashboard active records", slog.String("Error", err.Error())) return activerecords, err } defer rows.Close() for rows.Next() { var rec datamodel.ActiveRequestRecord err = rows.Scan(&rec.RequestNumber, &rec.RequestStatus, &rec.RequestorName, &rec.PendingWith, &rec.ProcessType, &rec.LastActionDate) if err != nil { logger.Error("Error while processing database resultset for dashboard active records", slog.String("Error", err.Error())) return activerecords, err } activerecords = append(activerecords, rec) } return activerecords, err } </code>
Request table structure:
<code>CREATE TABLE "REQUESTS" ( "REQUESTNUMBER" VARCHAR2(64 CHAR) NOT NULL ENABLE, "REQUESTSTATUS" VARCHAR2(128 CHAR) NOT NULL ENABLE, "SUBMISSIONDATE" TIMESTAMP(6), "PROCESSTYPE" VARCHAR2(256 CHAR), "SUBMITTER" VARCHAR2(256 CHAR) NOT NULL ENABLE, "REQUESTOR" VARCHAR2(512 CHAR), "PENDINGWITH" VARCHAR2(512 CHAR), "ACTIONDATE" TIMESTAMP(6), "RESUBMISSIONDATE" TIMESTAMP(6), PRIMARY KEY ( "REQUESTNUMBER" ), FOREIGN KEY ( "SUBMITTER" ) REFERENCES "SUBMITTERS" ( "USERNAME" ) ) </code>
mistake:
time=2023-10-04T06:43:06.304Z level=INFO source=C:/code/tutorials/myapp/internal/storage/dashboard.go:19 msg="Verify values" sortby=requestnumber sortorder=DESC startindex=0 pagesize=10 time=2023-10-04T06:43:06.603Z level=ERROR source=C:/code/tutorials/myapp/internal/storage/dashboard.go:34 msg="Error while executing prepared statement for retrieving dashboard active records" Error="ORA-00911: invalid character\n"
Workaround
The immediate problem is that you are using the JDBC-style ?
binding placeholder instead of the expected :var
form. From the documentation of the go-ora package, you say you are using: < /p>
So your stmt
should be:
SELECT requestnumber, requeststatus, NVL(requestor, 'N/A'), NVL(pendingwith, 'N/A'), NVL(processtype, 'N/A'), actiondate FROM requests WHERE requeststatus = 'PENDINGAPPROVAL' ORDER BY :sortby :sortorder OFFSET :startindex ROWS FETCH NEXT :pagesize ROWS ONLY
But you can't bind anything other than a variable, so it won't let you have sortorder
as a variable at all, if you just remove it and do:
ORDER BY :sortby OFFSET :startindex ROWS FETCH NEXT :pagesize ROWS ONLY
This seems to work, but even this doesn't do exactly what you want because the sort will sort by the literal column name rather than its value; so it will work as ORDER BY 'requestnumber'## The equivalent of # runs instead of
ORDER BY requestnumber. And sorting by that constant string won't accomplish anything.
"... ORDER BY " + sortby + " " + sortorder + " OFFSET :startindex ROWS FETCH NEXT :pagesize ROWS ONLY"
The above is the detailed content of How to resolve error 'ORA-00911: invalid character' in Golang?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











How to create tables using SQL statements in SQL Server: Open SQL Server Management Studio and connect to the database server. Select the database to create the table. Enter the CREATE TABLE statement to specify the table name, column name, data type, and constraints. Click the Execute button to create the table.

This article introduces a detailed tutorial on joining three tables using SQL statements to guide readers step by step how to effectively correlate data in different tables. With examples and detailed syntax explanations, this article will help you master the joining techniques of tables in SQL, so that you can efficiently retrieve associated information from the database.

phpMyAdmin can be used to create databases in PHP projects. The specific steps are as follows: Log in to phpMyAdmin and click the "New" button. Enter the name of the database you want to create, and note that it complies with the MySQL naming rules. Set character sets, such as UTF-8, to avoid garbled problems.

Methods to judge SQL injection include: detecting suspicious input, viewing original SQL statements, using detection tools, viewing database logs, and performing penetration testing. After the injection is detected, take measures to patch vulnerabilities, verify patches, monitor regularly, and improve developer awareness.

The methods to check SQL statements are: Syntax checking: Use the SQL editor or IDE. Logical check: Verify table name, column name, condition, and data type. Performance Check: Use EXPLAIN or ANALYZE to check indexes and optimize queries. Other checks: Check variables, permissions, and test queries.

The SQL INSERT statement is used to insert data into a table. The steps include: specify the target table to list the columns to be inserted. Specify the value to be inserted (the order of values must correspond to the column name)

MySQL has a free community version and a paid enterprise version. The community version can be used and modified for free, but the support is limited and is suitable for applications with low stability requirements and strong technical capabilities. The Enterprise Edition provides comprehensive commercial support for applications that require a stable, reliable, high-performance database and willing to pay for support. Factors considered when choosing a version include application criticality, budgeting, and technical skills. There is no perfect option, only the most suitable option, and you need to choose carefully according to the specific situation.

PostgreSQL The method to add columns is to use the ALTER TABLE command and consider the following details: Data type: Select the type that is suitable for the new column to store data, such as INT or VARCHAR. Default: Specify the default value of the new column through the DEFAULT keyword, avoiding the value of NULL. Constraints: Add NOT NULL, UNIQUE, or CHECK constraints as needed. Concurrent operations: Use transactions or other concurrency control mechanisms to handle lock conflicts when adding columns.
