I have got requirement to parse a JSON document that will be passed to a stored procedure inside a CLOB, and store its details into a DB2 table.
I cannot make use of JSON_TABLE function as I am still using IBM i V7R1.
Is there any way I can achieve this ?
Pre native built in support for JSON in 7.2 I used this third party tool ported to the iSeries and maintained by Scott Klement YAJL (Yet Another JSON Library)
I've used this apis on production. Excellent work.
Mihael Schmidt's Json Parser
Related
I have a ETL job built using spring batch and DAO layer uses Spring's jdbc template.The issue is with loading of numeric datatype. When the batch is running for large number of records, good amount of numeric values(not all) will be loaded incorrectly(pattern is that value will be multiplied by 10^scale).
I am using batchUpdate method and preparedStatement. The driver used is jconn4.jar from sybase version 7.0.7.
I am getting the values printed while setting the ps, and do not see the values being manipulated at java side.
Could someone please advice on what could be causing this.
Thanks in advance.
Edit: Further info Sybase version 15.7, Spring core and jdbc version 4.2.6, Spring batch version 3.0.4, java version 8
Also has someone used sybPreparedStatement from jConnect library? I found a sybase infocenter link where they recommend using it perticularly when using numeric data types but I do find the documentation around how to use this ps insignificant. Could you pl share if you have tried using SybPS and what were the challenges, and if you could successfully use that.
Is their any utility through which we can determine the list of database objects an Oracle Form or Report uses or the list of Forms and Reports that use a specific database object.
For Oracle forms/Reports 10g
There used to be a tool made by Quest Software "SQL Impact" but it is not supported any more.
The easiest way to do this kind of analysis is to convert all your fmb/rdf to xml and then write a script in Ruby searching for db object names.
Alternatively you can use JDAPI to iterate over forms objects, but there is no JDAPI for reports. Using JDAPI is much easier using JRuby, you can find sample scripts there:
https://github.com/tomi44g/OracleFormsJruby
We have some data in the SQL server table that needs to scramble. Some data are string and some data are date.
What is best way to do this?
Are you talking about Obfuscating your SQL Server Data? (To create a development version based on the production data without exposing the production data itself)
Or do you want it encrypted?
SQL Server 2005 introduced encryption support. Check out this article here.
i am using ADO.Net oledb for inserting and fetching data from Excel database. I want to make first column in the excel sheet to bold and i want to add comments. I am achieving this thru Interop.Excel Application class.
i dont want to use interop. is there anyway to achieve through ADO.net query itself ? or some other way? My application is c# windows application
No way through ADO.NET, any more than there is of making a SQL Server column bold. ADO.NET treats Excel as a data source - formatting is something quite different and requires knowledge of the Excel spreadsheet format, such as you'd get via Interop. There are probably other libraries you can use if you search...
I'm doing an iPhone application, and I'm using SQLite.
The problem is that I had some issues with the query (I did bad binding) so, this is my question:
How can I log in my iPhone application the effective SQL query/statement with the bindings that SQLite receives?
Thanks.
Easiest way would be to create a wrapper to your call to sql functions and add log functionality to it.
I'm not sure the file written by the PRAGMA journal_mode is readable, but I couldnt use this pragma.
You can also have a look at an excellent existing wrapper from Gus Mueller: fmdb
I don't think this is possible.
As far as I know, prepared statements aren't built into "full SQL" strings before they get to the database engine. The parameter values aren't escaped, quoted, and inserted into the SQL string only to be parsed and decoded in the next step: the values bypass the query parsing entirely and go straight into the data engine.