Encrypt() returns values with double quotes

I'm using encrypt to hide my state variables, but the results
have double
quotes which is killing my forms. Any suggestions? Is there a
range the
seed needs to be in to not produce double quotes.
Thanks,
Jeff

Experiment with a different key.

Similar Messages

SSIS importing comma delimited with double quote text qualifier - Works in VS - SQL Job ignores text qualifier and fails (truncation)

I've created an SSIS package to import a comma delimited file (csv) with double quotes for a text qualifier ("). Some of the fields contain the delimiter inside the qualified text. An example row is:
15,"Doe, John",IS2,Alabama
In SSIS I've specified the text qualifier as ". The sample output in the connection manager looks great. The package runs perfectly from VS and when manually executed on the SSIS server itself. The problem comes when I schedule the package to run via SQL
job. At this point the package ignores the text qualifier, and in doing so pushes half of a field into the next available column. But instead of having too many columns, it concatenates the last 2 columns ignoring the delimiter. For example (pipes are fields):
15|"Doe| John"|IS2,Alabama
So the failure happens when the last half of a field is too large to fit into the next available field. In the case above _John" is 6 characters where the IS2 field is char(3). This would cause a truncation failure, which is the error I receive from the
job history.
To further test this I created a failure flow in my data flow to capture the records failing to be pulled from the source csv. Out of ~5000 records, ~1200 are failing, and every one of the failures has a comma delimiter inside the quoted text with a 'split'
length greater than the next ordinal field. The ones without the comma were inserted as normal and records where the split fit into the next ordinal column where also imported, with the last field being concatenated w/delimiter. Example records when selected
from table:
25|"Allan Percone Trucking"|GI6|California --Imported as intended
36|"Renolds| J."|UI6,Colorado --Field position offset by 1 to right - Last field overloaded
To further ensure this is the problem, I changed the csv file and flat file connection manager to pipe delimited, and sure enough every record makes it in perfectly from the SQL job execution.
I've tried comma delimited on the following set ups. Each set up failed.
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 100
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 100
Since a lot of our data comes in via comma delimited flat files, I really need a fix for this. If not I'll have to rebuild all my files when I import them to use pipe delimiters instaed of commas. I'd like to avoid the extra processing overhead if possible.
Also, is this a known bug? If so can someone point me to the posting of said bug?
Edit: I can't ask the vendor to change the format to pipe delimited because it comes from a federal government site.

Just wanted to share my experience of this for anyone else since I wasted a morning on it today.
I encountered the same problem where I could run the package fine on my machine but when I deployed to a server and ran the package via dtexec, the " delimeter was being replaced with _x0022_ and columns all slurped up together and overflowing columns/truncating
data etc.
Since I didn't want to manually hack the DTS XML and can't install updates, the solution I used was to set an expression on the textdelimiter field of the flat file connection with the value "\"" (a double quote). That way, even if the one stored in XML
gets bodged somewhere along the way, it is overridden with the correct value at run time. The package works fine everywhere now.

How to replace single quote with double quote

hai all,
i have a problem,
i am trying insert a string containing single quote into ms-access database.
it is giving error.
how can i avoid this .if i replace a single quote in the text with double quote it will defenitely
insert into database.
in java.lang.String
replace () will not work to replace quote with double quote.
any otherway to solve this problem.
please mail me to [email protected]
thank you
sambareddy
inida

java.lang.String.replace () will not work to replace quote with double quote.Really?
String x = ...
x.replace( "'", "\"" );

Csv with double quotes

Hello,
I've had harsh time trying to figure out how to read a csv file with double quotes, I need to read a csv file in order to fill a spreadsheet.
I attach a csv file example to show the sort of file I'm working on.
Thank you
Raymundo Cassani
Solved!
Go to Solution.
Attachments:
test_file.csv ‏1 KB

Upon closer inspection, you are right, it was a trick question. You need to look for commas that follow an even number of quotation marks for the separators. Since my previous snippet was not converted, I assume you have an earlier LV version so I have attached an example in 8.6. You can get rid of the quotes if you like (exercise for the reader).
Attachments:
ReadCSVwithQuotes.vi ‏9 KB

8.1.7 jdbc driver: object types with double quotes

Hi all,
While switching from 8.1.6 to 8.1.7 I have trouble with the jdbc driver. It doesn't work
as before: The function CallableStatement.registerOutParameter (and probably some other) doesn't take object type
names in double quotes anymore. A test program is appended to this message. Using a 8.1.6 jdbc driver this program works fine but with a 8.1.7 jdbc driver it throws an exception.
My questions are: Is this bug already filed?
Is a bugfix already available somewhere?
Thanks in advance for any information
Joerg
import java.sql.*;
* create type "test_t" as object (atrb number(10));
* create table "test" of "test_t" (atrb not null) oidindex();
class test
public static void main (String args [])
throws SQLException
String s = "begin insert into \"test\" t values (1)" +
" returning ref(t) into ?; end;";
try{
DriverManager.registerDriver(new
oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:@host:1521:orcl","joerg", "password");
CallableStatement cs = conn.prepareCall( s );
cs.registerOutParameter(1, Types.REF, "\"test_t\"");
cs.execute();
System.out.println("Statement returned:");
System.out.println( cs.getObject(1) );
cs.close();
conn.commit();
conn.close();
catch(SQLException e){
System.out.println("SQLException was thrown...");
System.out.println(e.getMessage());
}

I believe that typenames are always treated as case sensitive (unless they are all uppercased).
In your example you should write:
cs.registerOutParameter(1, Types.REF, "test_t");
If you had declared the type test_t in a case insensitive way (without "..."), then you'd have to write:
cs.registerOutParameter(1, Types.REF, "TEST_T");
If you have a schema-qualified name, use a ".":
cs.registerOutParameter(1, Types.REF, "SCOTT.test_t");
However, this behavior implies that you cannot use "." inside of quoted identifier names.

JS - surrounding selected text with double quotes

I have a working script which places brackets around selected text in the main body of my document (not in a table), but when I changed the script to insert double curly quotes, the script wont work.
Why wont this JS work (script stalls on the var line):
var myObject = (app.selection[0].parent.constructor.name == "Cell") ? app.selection[0].parent.texts[0] : app.selection[0];
with (myObject)
insertionPoints[-1].contents = "";
insertionPoints[0].contents = "";
while this one does work:
var myObject = (app.selection[0].parent.constructor.name == "Cell") ? app.selection[0].parent.texts[0] : app.selection[0];
with (myObject)
insertionPoints[-1].contents = ")";
insertionPoints[0].contents = "(";
Thx Oz
PS The quotes are showing as three straight quotes above, but in my script they are two straight double quotes surrounding either a right or a left curly double quote.

Perhaps there's a Smart Quotes interpreter in JS? Who knows.
If you find it failing again, try inserting the quotes as Unicode values, as these should not be subject to any translating.
I.e.,
>insertionPoints[-1].contents = "\u201c";

Update with double quotes

Hi,
How to include double quotes in a update statement?
UPDATE sampletable
SET description = ' Message to Employee '
WHERE empid = 1;
Expected output with I query table,
select description from sampletable WHERE empid = 1;
 Error Message 
Table definition:
sampletable
empid number
description varchar2(200)
Thanks

Please use the {noformat}{noformat} tag at the beginning and end of your examples.SQL> create table sampletable( empid number, description varchar2(2000));
Table created.
SQL> insert into sampletable values (1, null);
1 row created.
SQL> UPDATE sampletable
2 SET description = ' Message to Employee '
3 WHERE empid = 1;
1 row updated.
SQL> select * from sampletable;
EMPID
DESCRIPTION
1
 Message to Employee 
Your question is not clear: why are you expecting "Error Message" instead of "Message to Employee"?
What do the double quotes have to do with it?

List Manager based on LOV returning values with missing spaces

I am using a list manager based on a pop up lov, in this case it is a list of supplier names. When the pop-up list is shown the values are displayed as expected, with all spaces intact. When I click the supplier name, and then click Add to add to the list manager, all spaces in the supplier name are lost.
The field I'm pulling is a varchar2 in the db. Here's the sql behind the lov:
select '(All Suppliers)' d, '(All Suppliers)' r from rep_gy_spend
union
select distinct supplier_name d, supplier_name r
from rep_gy_spend
order by 1
Any ideas on why the spaces are lost?

DJ - There is a javascript function on the page that does that. View page source and you'll see it. You could override it with your own and change that behavior and you could prevent it from upper-casing the returned values as well by using different onclick javascript on the add button.
Scott

Query filters with double quotes fail

Hi,
when I to execute a query with a filter that contains double quotes on
Kodo 3.0.3 I get an Exception.
Filter:
string == \"My name is \"Wolfgang\".\"
Kodo interprets the double quotes (after 'is ' )as the end of the string
and expects the next token ('Wolfgang') to be an attribute name.
Is there an escape character for double quotes or any other solution?
Exception:
kodo.util.UserException: Attempt to query nonexistant or unm
anaged field "Wolfgang" of type "de.logas.datenbank.jdo.BeispielKlasse1".
at kodo.query.FilterParser.traversePath(FilterParser.java:1061)
at kodo.query.FilterParser.eval(FilterParser.java:783)
at kodo.query.FilterParser.getValue(FilterParser.java:999)
at kodo.query.FilterParser.eval(FilterParser.java:813)
at kodo.query.FilterParser.getExpression(FilterParser.java:1021)
at kodo.query.FilterParser.parseFilter(FilterParser.java:204)
at
kodo.query.JDOQLQuery$DataStoreQueryExecutor.<init>(JDOQLQuery.java:4
27)
at
kodo.query.JDOQLQuery.newDataStoreQueryExecutor(JDOQLQuery.java:99)
at kodo.query.AbstractQuery.internalCompile(AbstractQuery.java:576)
at kodo.query.AbstractQuery.compile(AbstractQuery.java:531)
at kodo.datacache.CacheAwareQuery.compile(CacheAwareQuery.java:271)
-- Wolfgang

Also, in general, it is advantageous to separate variable content in a
query out into parameters. This helps us out when maintaining our query
compilation cache.
-Patrick
Stephen Kim wrote:
Wolfgang,
To do this in JDO you have to double escape it
i.e. string== \"My name is \\\"Wolfgang\\\".\"
Wolfgang Hutya wrote:
Hi,
when I to execute a query with a filter that contains double quotes on
Kodo 3.0.3 I get an Exception.
Filter:
string == \"My name is \"Wolfgang\".\"
Kodo interprets the double quotes (after 'is ' )as the end of the string
and expects the next token ('Wolfgang') to be an attribute name.
Is there an escape character for double quotes or any other solution?
Exception:
kodo.util.UserException: Attempt to query nonexistant or unm
anaged field "Wolfgang" of type "de.logas.datenbank.jdo.BeispielKlasse1".
at kodo.query.FilterParser.traversePath(FilterParser.java:1061)
at kodo.query.FilterParser.eval(FilterParser.java:783)
at kodo.query.FilterParser.getValue(FilterParser.java:999)
at kodo.query.FilterParser.eval(FilterParser.java:813)
at kodo.query.FilterParser.getExpression(FilterParser.java:1021)
at kodo.query.FilterParser.parseFilter(FilterParser.java:204)
at
kodo.query.JDOQLQuery$DataStoreQueryExecutor.<init>(JDOQLQuery.java:4
27)
at
kodo.query.JDOQLQuery.newDataStoreQueryExecutor(JDOQLQuery.java:99)
at
kodo.query.AbstractQuery.internalCompile(AbstractQuery.java:576)
at kodo.query.AbstractQuery.compile(AbstractQuery.java:531)
at
kodo.datacache.CacheAwareQuery.compile(CacheAwareQuery.java:271)
-- Wolfgang

View Columns with Double Quotes

When Creating a view I specify Column Names, but when you look at the SQL tab it puts double quotes around the columns is there a preference to turn this off? Is there a reason for it operating this way?
CREATE OR REPLACE FORCE VIEW "MCT"."V_USER_ORGANIZATIONS" (CUSTOMERS_ID, CUSTOMER_NAME) AS
SELECT Customers_ID, Customer_Name FROM mct.Customers
UNION ALL
SELECT Proc_Offices_ID *-1 as Customers_ID, Proc_Office_Name as Customer_Name FROM mct.proc_offices;
becomes the following
CREATE OR REPLACE FORCE VIEW "MCT"."V_USER_ORGANIZATIONS" ("CUSTOMERS_ID", "CUSTOMER_NAME") AS
SELECT Customers_ID, Customer_Name FROM mct.Customers
UNION ALL
SELECT Proc_Offices_ID *-1 as Customers_ID, Proc_Office_Name as Customer_Name FROM mct.proc_offices;

The only control we have over the DDL that is generated are the options in Tools > Preferences > Database > ObjectViewer Parameters, which doesn't include an option to exclude unnecessary double quotes.
The reason why they are put in when generating the DDL is to simplify the logic of generating the DDL - if they were not there, it would be necessary to check if names were in mixed case or not. For example, it would be possible to create a view as follows:
CREATE OR REPLACE FORCE VIEW "My_View" ("Customer_ID", "Customer_Name") AS ...
With this, I have explicitly said that my view and column names are case sensitive - and this is NOT equivalent to:
CREATE OR REPLACE FORCE VIEW MY_VIEW (CUSTOMER_ID, CUSTOMER_NAME) AS ...
That being said, as I understand it, SQL Developer uses the DBMS_METADATA package to generate the DDL and the inclusion of the double quotes is presumably the standard option with that.
theFurryOne

Replace Single Quote with double quote

Hi All,
I have a String s="help'me'to'replace";
i want to replace single quote( ' ) in to double quote ( " )
The final out put should be like this help"me"to"replace
( Actually this string i have to pass in to an XML )
Please help any one

s.replaceAll("'","\"");{code}
or just one of the String#replace() methods.
Edited by: sabre150 on Mar 17, 2009 11:48 AM

Can't import csv fields starting with double quotes but lack ending ones

Hi all,
When I'm trying to used external table to import a csv file, specified as using comma as delimiter optionally enclosed by double quotes, some records are rejected because a field in the record has starting double quotes, but without ending ones.
Assume the customer really want these starting double quotes, how do I change my external table specification such that these starting double quotes are treated as part of the field data and can be successfully inserted into db?
Many thanks.

I have no access to Oracle during weekends, so nothing can be tested. So here it goes:
Suggestion: DELIMITED BY '","' and of course omitt ENCLOSED BY '"'
You will have to update each row of the rows just loaded setting the first_field to substr(first_field,2) and the last_field to substr(last_field,-2)
If all the fields are not enclosed in double quotes (TRUE for strings and FALSE for numbers and dates) the situation (syntax diagrams allow two delimiters only) is somehow more complicated, anyway you can specify DELIMITED BY ',' and update all varchar2 fields in each row of the rows just loaded setting the varchar2_field to substr(varchar2_field,2,length(varchar2_field) - 2).
Regards
Etbin
After posting I noticed it's difficult to distinguish between single and double quotes:
the first DELIMITED BY should read {single quote){double quote}{comma}{double quote}{single quote)
the ENCLOSED BY should read {single quote){double quote}{single quote)
Message was edited by: Etbin
user596003

Sequence.nextval doubles the returned value with Execute Statement (F9)

There appears to be a quirk with sequences in Raptor.
Has anyone noticed that depending on how you execute this sql (SELECT MYSEQ.NEXTVAL FROM DUAL;) the value returned is either the correct nextval or double what you expected?
For example, MYSEQ is a simple sequence which increments by 1. If you Execute Statement (F9) then the value returned jumps by 2 instead of 1. If you Run Script (F5) then the value returns jumps by 1, as expected.
If MYSEQ is changed to increment by 2. The when you Execute Statement (F9) then the value returned jumps by 4 instead of 2. If you Run Script (F5) then the value returns jumps by 2, as expected. No matter what you put for the increment by Execute Statement (F9) always doubles it.
It always seems to be double. Executing the same scenario in TOAD always returns the correct value (i.e. properly increments).
Is the query being executed multiple times with Execute Statement? Why is this happening?

While there is no guarantee from Oracle that sequences produce sequential numbers, this is obviously a case where SQL Developer is running the select statement twice.
The issue is that queries can actually change information, rather than just retrieve data from the database.
The following package is a test case:
create or replace package test_query is
function get_next_count return number;
end;
create or replace package body test_query is
cnt number := 0;
function get_next_count return number is
begin
cnt := cnt + 1;
return cnt;
end;
end;
select test_query.get_next_count from dual;
This query, which should return 1, 2, 3, 4, etc actually returns 2, 4, 6, 8, etc, because SQL Developer is running the select twice.

Issue with double quotes in APEX 3.1

Hi,
Recently we have upgraded our APEX environment (both production and development) from HTMLDB 2.0 to APEX 3.1.
Users reported that when they cut/paste data from word document into forms, double and single quotes in the data are displaying as weird symbols like "¿".
Surprisingly we have this issue in our production environment only not in development environment. I am guessing there must be setting which is causing this issue.
Please help me to resolve the issue and let me know if you want more details.
Thanks,
Lakshmi

It's most likely this is caused by non-standard Microsoft character encoding in combination with default "auto correct" behaviour in their products that users may not even be aware is operating. "Smart Quotes" are the culprit in this case.
As it is highly unlikely that your users will be able to stop using these products, the best options are: turn off the offending features in MS software; educate users about the source of the problem and get them to replace the errant characters with the relevant ASCII or Unicode character or "decimal numeric character reference" when transferring to DB/web (worthwhile bearing some context in mind here: ASCII apostrophes and quotes are probably best for values stored in traditional database columns as they may be used in a number of different applications); try to write some kind of translator in your database/application that fixes the incorrect characters.
That this is occurring in one environment but not the other may indicate that there's a character set difference somewhere in the stack, but the human element may be coming into play as well: developers encounter this problem frequently and often turn off "smart quotes" as a result!

HttpServletRequesr.getParameter : Problem with double quotes

Hi,
I am having a problem in accessing "POST" parameters which have "quotes" in it. For example,
If the post parameter named param contains Hello "(hw)" World, the getParameter returns Hello instead of Hello "(hw)" World.
I'm not sure if this is related to encoding. Encoding seem to be ISO-8859-1 (got from getCharacterEncoding).
Any clue of the problem ?

How do you send the post parameters. Do you send them usign a html from or are you sending them programaticaly. In that case make sure the keys and values are URL encoded with UTF-8

Encrypt() returns values with double quotes

Similar Messages

Maybe you are looking for