JXTable with long column

I am using JXTable. I have a model class which extends AbstractTableModel. My JXTable has one Long column. When the values are displayed, it display with a comma. For example if the value is 1000, in the table it is displayed as 1,000. But I want to display it as 1000.
Please let me know what should I do to display the field without comma.

Well, that would be JXTable "feature".
The default JTable, does not display the comma. So you need to customize the renderer.
Check out the [Table Format Renderers|http://www.camick.com/java/blog.html?name=table-format-renderers] for a simple way to get started.

Similar Messages

Change Tablespace of a table with LONG column

I have a 9i database that I have just gotten control of. At this point there is just one big dictionary managed tablespace for everything created by users. I am trying to move to multiple locally managed tablespaces with fixed extent sizes but I have run into a problem.
I have one table with one LONG datatype column. Apparently there is a huge amount of work involved to change the code if I make it a BLOB so that is out.
At this point I would like to change the tablespace of this table but I can't move it the normal way because of the LONG column. I have found mention of being able to do this with "COPY" but I can't find any documentation on the "COPY" command in the 9i Docs.
Any help would be appreciated,
Chris S.

Chris-
Can't you create your new table ahead of time in your new tablespace?
You could then use a statement like:
COPY FROM old/your_password@olddb TO new/your_password@newdb -
REPLACE NEWTABLE -
USING SELECT * FROM OLDTABLE;

Selecting from a SQL Server 2005 with long column names ( 30 chars)

Hi,
I was able to set up a db link from Oracle 11.2.0.1 to SQL Server 2005 using DG4ODBC.
My problem is that some column names in the Sql Server are longer than 30 chars and trying to select them gives me the ORA-00972: identifier is too long error.
If I omit these columns the select succeeds.
I know I can create a view in the sql server and query it instead of the original table, but I was wondering if there's a way to overcome it with sql.
My select looks like this:
select "good_column_name" from sometable@sqlserver_dblink -- this works
select "good_column_name","very_long_column_name>30 chars" from sometable@sqlserver_dblink -- ORA-00972Thanks

I tried creating a view with shorter column names but selecting from the view still returns an error.
create view v_Boards as (select [9650_BoardId] as BoardId, [9651_BoardType] as BoardType, [9652_HardwareVendor] as
HardwareVendor, [9653_BoardVersion] as BoardVersion, [9654_BoardName] as BoardName, [9655_BoardDescription] as BoardDescription,
[9656_SlotNumber] as SlotNumber, [9670_SegmentId] as SegmentId, [MasterID] as MasterID, [9657_BoardHostName] as BoardHostName,
[9658_BoardManagementUsername] as BoardManagementUsername, [9659_BoardManagementPassword] as BoardManagementPassword,
[9660_BoardManagementVirtualAddress] as BoardManagementVirtualAddress, [9661_BoardManagementTelnetLoginPrompt] as
MANAGEMENTTELNETLOGINPROMPT, [9662_BoardManagementTelnetPasswordPrompt] as MANAGEMENTTELNETPASSPROMPT,
[9663_BoardManagementTelnetCommandPrompt] as MANAGEMENTTELNETCOMMANDPROMPT FROM Boards)performing a select * from this view in sqlserver works and show the short column names
this is the error i'm getting for performing a select * from v_boards@sqlserver_dblink
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Microsoft][SQL Native Client][SQL Server]Invalid column name 'BoardManagementTelnetLoginProm'. {42S22,NativeErr = 207}[Microsoft]
[SQL Native Client][SQL Server]Invalid column name 'BoardManagementTelnetPasswordP'. {42S22,NativeErr = 207}[Microsoft][SQL Native
Client][SQL Server]Invalid column name 'BoardManagementTelnetCommandPr'. {42S22,NativeErr = 207}[Microsoft][SQL Native Client][SQL
Server]Statement(s) could not be prepared. {42000,NativeErr = 8180}
ORA-02063: preceding 2 lines from sqlserver_dblinkI also tried replacing the * with specific column names but it fails on the columns that have a long name (it doesn't recognize the short names from the view)
what am I doing wrong?
Edited by: Pyrocks on Dec 22, 2010 3:58 PM

Problem with LONG column in 8.1.7

Hello All,
Our db version is 8.1.7.0.0. ( Unix OS ).
We have a table with a LONG column, which stores BINARY data(Billing Details). Is there any way to manipulate it, other than converting it to LOB column?
I dont know where to start.Any help or hint is appreciated..
Thanks..

I did the following test in 10g but not with 8i:
dev001> set serveroutput on
dev001>
dev001> declare
2 v_b blob;
3 v_c varchar2(10);
4 begin
5 v_b := utl_raw.cast_to_raw('OK');
6 v_c := utl_raw.cast_to_varchar2(v_b);
7 dbms_output.put_line(v_c);
8 end;
9 /
OK
PL/SQL procedure successfully completed.However it is not a good idea to use BLOB data type to store character data: you should use CLOB for character data and BLOB for binary data.

Strange behavior in BI Publisher with long column names from BI Answers

Hello all!
I have created a BI Answers request with few calculated columns in form of
case when <condition> then <value if true> else <value if false> end
Then in BI Publisher Desktop designed a report ttemplate based on saved BI Answers request and noticed that for calculated columns their names look strange:
CASEWHEN_<condition>THEN...ELSE..._...END__
Some of the column names are about 100 characters long.
After running the report from Word found that for these "long length named columns" there's no data in the output.
Do someone else experience the same? Any workarounds?
Regards,
mr.maverick

This is because the length for the formula is restricted in publisher. you have to either reduce the size of the column name in answers or change the formula. another workaround is completely pasting the formula directly in the word template instead of placing the formula inside the form field. you can add maximum of 300 characters i guess. you can edit the formula for the form field in the form field options formuals menu.

Report with long column cell value

Hi,
we have report with some number of columns and some columns cells have value with a lot of chars (more than 100). We would like to trim this column cell value to for example 20 chars and put all chars of column cell value to HTML TD title value as "hint". Something like this:
<code>
<td #ALIGNMENT# headers="#COLUMN_HEADER_NAME#" title="#FULL_COLUMN_VALUE#" class="data">#TRIMED_COLUMN_VALUE#</td>
</code>
It is possible do this by template? Do you have any idea?
I have one idea that use JavaScript and full column value in hidden column, but I thing that there could be some better way to do this:-)
With regards.
David
Edited by: user4893970 on Nov 23, 2010 4:11 PM

While I don't think there's any way to do this with a normal reportIf it is a standard report and not an interactive report, then it can be done using the column HTML Expression:
<span title="#FULL_COLUMN_VALUE#">#TRIMMED_COLUMN_VALUE#</span>

Problem with long column names

I'm trying to fetch rows via pl/sql from an Access db table that has long(over 30 characters) column names. I've tried using pass-through sql but it still returns generic ODBC error. Is there a way to get this to work without changing column names in table?

Andy,
Oracle does have a restriction in column name size but if you are using pass-through this should not come into play.
It may be a restriction of the ODBC driver or a bug. Please take a look at the ODBC driver trace file.
Vira

Working with Long columns

hello, I have a LONG in a table that stores RTF format, I need to show the RTF into a JTextPane, Can anybody help me with it. thanks for you help!!!!

Hi George,
Select the cell with the formula and the cells beneath it that you want to fill with the formula, then go to the Calculate menu and choose Fill Down.
You can also fill in formulas or values to the right of the original cell using the Fill Right command.
Keyboard shortcuts for the two commands are command-D and command-R respectively.
Regards,
Barry

How to create a concatenated index with a long column (Urgent!!)

We have a situation where we need to create a concatenated unique
index with one of the columns as a "long" datatype. Oracle does
not allow a lot of things with long columns.
Does anyone know if this is possible or if there is a way to get
around it.
All help is appreciated!!!!

From the Oracle SQL Reference ...
"You cannot create an index on columns or attributes whose
type is user-defined, LONG, LONG RAW, LOB, or REF,
except that Oracle supports an index on REF type columns
or attributes that have been defined with a SCOPE clause."
Doesn't mention CLOB or BLOB types, so perhaps you
should consider using one of those types instead. I have a
feeling that the LONG type is now deprecated.

Table with a Long column

I had a problem, when i am creating a table with the SQL -->
"create table tab2 as (select * from tab1); "
i get an error --> ORA-00997: illegal use of LONG datatype
This i figured out happened because tab1 has a long column.
How to recreate a table with long column ?
null

You could use the COPY feature once your second table is created:
DROP TABLE one
DROP TABLE two
CREATE TABLE one
(n NUMBER
,l LONG)
INSERT INTO one
VALUES
(1
,'123'
CREATE TABLE two
(n NUMBER
,l LONG)
COPY FROM apps/apps@dblink TO apps/apps@dblink APPEND two USING SELECT * FROM one
SELECT * FROM one
SELECT * FROM two
null

Using DBMS_DATAPUMP with LONG data type

I've got a procedure below that calls the DBMS_DATAPUMP procedure using a REMOTE_LINK to move a schema from one database to another. However, a couple of the tables within that schema have columns with the LONG data type. And when I run it I get an error saying that you cannot move data with the LONG data type using a REMOTE LINK. So no data in those particular tables gets moved over.
Has anyone else had this issue? If so, do you have a work around? I tried adding a CLOB column to my table and setting the new CLOB to equal the LONG, but I couldn't get that to work either...even when I tried using a TO_LOB. If I could get that to, then I could just drop the LONG, move the schema, then recreate the LONG column on the opposite side.
Here's my procedure....
DECLARE
     /* EXPORT/IMPORT VARIABLES */
     v_dp_job_handle                    NUMBER ;          -- Data Pump job handle
     v_count                              NUMBER ;          -- Loop index
     v_percent_done                    NUMBER ;          -- Percentage of job complete
     v_job_state                         VARCHAR2(30) ;     -- To keep track of job state
     v_message                         KU$_LOGENTRY ;     -- For WIP and error messages
     v_job_status                    KU$_JOBSTATUS ;     -- The job status from get_status
     v_status                         KU$_STATUS ;     -- The status object returned by get_status
     v_logfile                         NUMBER ;
     v_date                              VARCHAR2(13) ;
     v_source_server_name          VARCHAR2(50) ;
     v_destination_server_name     VARCHAR2(50) ;
BEGIN
     v_project := 'TEST' ;
     v_date := TO_CHAR(SYSDATE, 'MMDDYYYY_HHMI') ;
     v_source_server_name := 'TEST_DB' ;
     v_dp_job_handle := DBMS_DATAPUMP.OPEN(
          OPERATION     => 'IMPORT',
          JOB_MODE     => 'SCHEMA',
          REMOTE_LINK => v_source_server_name,
          JOB_NAME     => v_project||'_EXP_'||v_date,
          VERSION          => 'LATEST') ;
     v_logfile := DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE ;
     DBMS_DATAPUMP.ADD_FILE(
          HANDLE          => v_dp_job_handle,
          FILENAME     => v_project||'_EXP_'||v_date||'.LOG',
          DIRECTORY     => 'DATAPUMP',
          FILETYPE     => v_logfile) ;
     DBMS_DATAPUMP.METADATA_FILTER(
          HANDLE          => v_dp_job_handle,
          NAME          => 'SCHEMA_EXPR',
          VALUE          => '= '''||v_project||''' ') ;
     DBMS_DATAPUMP.START_JOB(v_dp_job_handle) ;
     v_percent_done := 0 ;
     v_job_state := 'UNDEFINED' ;
     WHILE (v_job_state != 'COMPLETED') AND (v_job_state != 'STOPPED')
     LOOP
          DBMS_DATAPUMP.GET_STATUS(
               v_dp_job_handle,
               DBMS_DATAPUMP.KU$_STATUS_JOB_ERROR + DBMS_DATAPUMP.KU$_STATUS_JOB_STATUS + DBMS_DATAPUMP.KU$_STATUS_WIP,
               -1,
               v_job_state,
               v_status) ;
               v_job_status := v_status.JOB_STATUS ;
          IF v_job_status.PERCENT_DONE != v_percent_done THEN
               DBMS_OUTPUT.PUT_LINE('*** Job percent done = '||TO_CHAR(v_job_status.PERCENT_DONE)) ;
               v_percent_done := v_job_status.PERCENT_DONE ;
          END IF ;
          IF BITAND(v_status.MASK, DBMS_DATAPUMP.KU$_STATUS_WIP) != 0 THEN
               v_message := v_status.WIP ;
          ELSIF BITAND(v_status.mask, DBMS_DATAPUMP.KU$_STATUS_JOB_ERROR) != 0 THEN
               v_message := v_status.ERROR ;
          ELSE
               v_message := NULL ;
          END IF ;
          IF v_message IS NOT NULL THEN
               v_count := v_message.FIRST ;
               WHILE v_count IS NOT NULL
               LOOP
                    DBMS_OUTPUT.PUT_LINE(v_message(v_count).LOGTEXT) ;
                    v_count := v_message.NEXT(v_count) ;
               END LOOP ;
          END IF ;
     END LOOP ;
     DBMS_OUTPUT.PUT_LINE('Job has completed') ;
     DBMS_OUTPUT.PUT_LINE('Final job state = '||v_job_state) ;
     DBMS_DATAPUMP.DETACH(v_dp_job_handle) ;
END ;

But the application we have that uses the database cannot be changed to read from a CLOBWhy can't you change the application?
Well, anyway you should point out to your superiors that Oracle documented years ago to not use LONGS anymore...
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/datatype.htm#sthref3806
It clearly states:
LONG Datatype
Note:
Do not create tables with LONG columns. Use LOB columns (CLOB, NCLOB) instead. LONG columns are supported only for backward compatibility.
Oracle also recommends that you convert existing LONG columns to LOB columns. LOB columns are subject to far fewer restrictions than LONG columns. Further, LOB functionality is enhanced in every release, whereas LONG functionality has been static for several releases.
How do I go from CLOB to LONG?I'm sorry, cannot help you on that one, I don't think you can do that at all (Oracle wants us to stop using LONGS, so, it's a one-way conversion...):
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1037232794454#15512131314505
So: NO built_in, you'll need to write a program if the clob is ALWAYS LESS THAN 32k in size, you can use plsql..but is that the case in your case? Only you know that.
I believe that question is still unanswered on this forum, but you might try searchin for answers on this forum, and
the 'Database-General' forum: General Database Discussions
Perhaps you can google a Q&D workaround...
( And consider convincing your collegues to just convert your LONGS to LOBS)
Edited by: hoek on Apr 8, 2009 5:43 PM

Select LONG column from Remote table

Hi to all.
I have the following problem: I can't select a LONG column from remote database, when there are Join operation in the query. Example:
SELECT long_column FROM remote_table@DB
-> that's OK, but:
SELECT long_column FROM remote_table@DB INNER JOIN remote_table2@DB ON ...
-> returns: "ORA-00997: Illegal use of LONG datatype"
I cannot even perform (because there a LONG column in the joined table):
SELECT nonlong_column FROM remote_table@DB INNER JOIN remote_table2@DB ON ...
That's very strange to me because:
SELECT long_column FROM local_table INNER JOIN local_table2 ON ...
-> is OK!
Can someone help me to SELECT a long column from remote in SELECT query with JOIN clause!
Thanks a lot!

Hi
"Distributed queries are currently subject to the restriction that all tables locked by a FOR UPDATE clause and all tables with LONG columns selected by the query must be located on the same database. " by otn docs.
I have no idea.
Ott Karesz
http://www.trendo-kft.hu

Exporting a table with Long datatype col. name

Hello,
I need help exporting a table, One of the column is long datatype.
How can I do this without using Export Util?
Is it possible.
(If someone has a solution then PLEASE Email
me)
URGENT.
Thanks.
Pankaj Patel.

Just wanted to find out, if you already solved this problem. I have a similar issue with long column. I am trying to sql dump a table with long column that will be imported into another database(probably using sql*load), but the spooled file puts the data from the long column in separate lines 80 char long and not on a single line. I have set the long to 64000 and linesize to 32000. Wrap is on too.
null

I recently began using reminders in ical and downloaded the iPhone and iPad app. It works great. However, the reminders in ical on the COMPUTER is difficult to work with - thin long column on the right rather than in it's own screen. is there a reminders

I recently began using reminders in ical and downloaded the iPhone and iPad app. It works great. However, the reminders in ical on the COMPUTER is difficult to work with - thin long column on the right rather than in it's own screen. is there a reminders app for the COMPUTER that is more user friendly?

sgreenie,
If you are willing to wait, Apple - OS X Mountain Lion - Inspired by iPad. Made for the Mac explains that a "Reminders" application will be included in the next release of OS X.

How to retrieve 'long' column with 32K length in Java stored procedure

For some reasons, we are not using CLOB, BLOB, or BFILE to store large objects and I have to live with LONG. So I wrote a Java stored procedure to insert, select and manipulate a LONG column by retrieving the LONG into a java.lang.String class (which happens to be the Java class mapped to the LONG SQL datatype). It all works fine as long as the length of the value being retrieved is less than the magic figure of 32767 bytes (which is the restriction on LONG and VARCHAR2 datatype in PL/SQL as well). So looks like Oracle's implementation of the JVM limits String values to a max of 32767 bytes. Suggestions on how to overcome this limitation (other classes that you suggest or do I have to move to files)?
Thanks,
Jeet
null

the jvm has nothing to do with it ...
this is a pol/sql limitation on parameters in stored procedures.
and java stored procedures require a clal spec that makes the j-s-p look like a pl/qsl stored proc.

JXTable with long column

Similar Messages

Maybe you are looking for