Giter Site home page Giter Site logo

Comments (8)

felipebz avatar felipebz commented on May 17, 2024

All links are dead now, I'm not sure why.

from zpa.

slachiewicz avatar slachiewicz commented on May 17, 2024

Actual repository cam be found here: https://github.com/oracle/oracle-db-tools

from zpa.

felipebz avatar felipebz commented on May 17, 2024

Hi @slachiewicz. Actually not. The oracle-db-tools repository contains only sample code showing how to use SQLcl as a library in a project. The (now removed) dbtools-commons had the actual source code of SQLcl and some libraries shared between it and SQL Developer.

from zpa.

martinmlouis avatar martinmlouis commented on May 17, 2024

Hi, I tried to format a file and send output to a new file and if there are no errors in the input file it is fine, but if there are some errors in the input file it just says "parser error" and no line numbers where the error happened. Not sure if this is the intended functionality. A line number and the usual oracle error message information will be good for automating SQLcl

from zpa.

felipebz avatar felipebz commented on May 17, 2024

@martinmlouis sorry, but I didn't understand what you are doing. I think you are in the wrong repository...

from zpa.

martinmlouis avatar martinmlouis commented on May 17, 2024

Hi, This is regarding SQLcl. I used it to format a SQL file hoping to get exact errors.
format file input.sql output.sql
If there is no errors the parser silently exits successfully.
If there is an errors it just says "parser error" and does not give me the exact place where the error happened.
I am trying to validate/check_syntax for SQL files using SQLcl
Any insight on getting this done will be helpful for me,
Thanks

from zpa.

felipebz avatar felipebz commented on May 17, 2024

@martinmlouis I'm afraid I can't help you... Please try to start a new thread on https://community.oracle.com/community/database/developer-tools/sql_developer/sqlcl/content

from zpa.

martinmlouis avatar martinmlouis commented on May 17, 2024

Trying to use SyntaxError.checkSyntax class in sqlcli to check syntax
I am trying to automate sql syntax check using sqlcli supplied jar file dbtools-common.jar in the lib dir for sqlcl-18.2.0

Sometimes it gives me this error and I am not able to figure out what this means

Expected: name_wo_function_call,identifier,name,sim_stmt,sql

Expected: name_wo_function_call,identifier,name,labeled_nonb

Have anyone who used SQL Developer or SQLcl for chcking syntax errors faced this issue,

Any insight would be good for me,

Thanks,

from zpa.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.