dbTalk Databases Forums  

column_schema.setDefault problem

sybase.public.sqlanywhere.ultralite sybase.public.sqlanywhere.ultralite


Discuss column_schema.setDefault problem in the sybase.public.sqlanywhere.ultralite forum.

Reply
 
Thread Tools Display Modes
  #41  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 07:51 PM






There was a bug in the GA version that produced this problem, but it is
fixed and I do not see it in the EBF (11.0.0.1490). So either you have a
special case where there is still an issue or there is something else.

Have you seen this on device or in the emulator or both?

Sometimes I have had problems upgrading COD files on device and
emulator. On the emulator the best thing is to open a command prompt at
the \program files\research in motion\BlackBerry JDE <version>\simulator
directory and run "clean.bat" It takes several minutes to run, but it
does get rid of all installed COD files so that when you load a new one
you can be sure.

On device, it may be worth uninstalling UltraLiteJ and then adding the
new one, just to be sure again.

These procedures are not usually needed, but it seems there are some
times when just installing a new version doesn't overwrite the old version.

Tom Slee

GUO Lin wrote:
Quote:
It is about SQL UltraliteJ.

I have updated to the forth EBF release.
But I have still the problem about the function setDefault

1 : column_schema.setDefault( COLUMN_DEFAULT_GLOBAL_AUTOINC )

I define the table schema like this:

conn.schemaCreateBegin();
ColumnSchema column_schema;
TableSchema table_schema = conn.createTable("INTERVENTIONS");

column_schema = table_schema.createColumn( "id", Domain.INTEGER );
column_schema.setNullable( false );

column_schema.setDefault( ColumnSchema.COLUMN_DEFAULT_GLOBAL_AUTOINC );

column_schema = table_schema.createColumn( "description",
Domain.VARCHAR, 512 );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "statut",
Domain.INTEGER);
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "duree",
Domain.INTEGER );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "idtechnicien",
Domain.INTEGER);
column_schema.setNullable( true );
...

IndexSchema index_schema =
table_schema.createPrimaryIndex( "primary" );
index_schema.addColumn( "id", IndexSchema.ASCENDING );
conn.schemaCreateComplete();

When I insert data into this table, I receive an exception :
ULjException: ianywhere.ultralitej.implementation.JrException:
UltraLiteJ Error[-195]: Column 'id' in table 'INTERVENTIONS' cannot be
NULL

2: We have the function getLastIdentity of interface connection in M-
business.
But We have not the equivalencie in UltralitJ, has anyone good
solution of getting the last identity ?




Reply With Quote
  #42  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 07:51 PM






There was a bug in the GA version that produced this problem, but it is
fixed and I do not see it in the EBF (11.0.0.1490). So either you have a
special case where there is still an issue or there is something else.

Have you seen this on device or in the emulator or both?

Sometimes I have had problems upgrading COD files on device and
emulator. On the emulator the best thing is to open a command prompt at
the \program files\research in motion\BlackBerry JDE <version>\simulator
directory and run "clean.bat" It takes several minutes to run, but it
does get rid of all installed COD files so that when you load a new one
you can be sure.

On device, it may be worth uninstalling UltraLiteJ and then adding the
new one, just to be sure again.

These procedures are not usually needed, but it seems there are some
times when just installing a new version doesn't overwrite the old version.

Tom Slee

GUO Lin wrote:
Quote:
It is about SQL UltraliteJ.

I have updated to the forth EBF release.
But I have still the problem about the function setDefault

1 : column_schema.setDefault( COLUMN_DEFAULT_GLOBAL_AUTOINC )

I define the table schema like this:

conn.schemaCreateBegin();
ColumnSchema column_schema;
TableSchema table_schema = conn.createTable("INTERVENTIONS");

column_schema = table_schema.createColumn( "id", Domain.INTEGER );
column_schema.setNullable( false );

column_schema.setDefault( ColumnSchema.COLUMN_DEFAULT_GLOBAL_AUTOINC );

column_schema = table_schema.createColumn( "description",
Domain.VARCHAR, 512 );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "statut",
Domain.INTEGER);
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "duree",
Domain.INTEGER );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "idtechnicien",
Domain.INTEGER);
column_schema.setNullable( true );
...

IndexSchema index_schema =
table_schema.createPrimaryIndex( "primary" );
index_schema.addColumn( "id", IndexSchema.ASCENDING );
conn.schemaCreateComplete();

When I insert data into this table, I receive an exception :
ULjException: ianywhere.ultralitej.implementation.JrException:
UltraLiteJ Error[-195]: Column 'id' in table 'INTERVENTIONS' cannot be
NULL

2: We have the function getLastIdentity of interface connection in M-
business.
But We have not the equivalencie in UltralitJ, has anyone good
solution of getting the last identity ?


Reply With Quote
  #43  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 07:51 PM



There was a bug in the GA version that produced this problem, but it is
fixed and I do not see it in the EBF (11.0.0.1490). So either you have a
special case where there is still an issue or there is something else.

Have you seen this on device or in the emulator or both?

Sometimes I have had problems upgrading COD files on device and
emulator. On the emulator the best thing is to open a command prompt at
the \program files\research in motion\BlackBerry JDE <version>\simulator
directory and run "clean.bat" It takes several minutes to run, but it
does get rid of all installed COD files so that when you load a new one
you can be sure.

On device, it may be worth uninstalling UltraLiteJ and then adding the
new one, just to be sure again.

These procedures are not usually needed, but it seems there are some
times when just installing a new version doesn't overwrite the old version.

Tom Slee

GUO Lin wrote:
Quote:
It is about SQL UltraliteJ.

I have updated to the forth EBF release.
But I have still the problem about the function setDefault

1 : column_schema.setDefault( COLUMN_DEFAULT_GLOBAL_AUTOINC )

I define the table schema like this:

conn.schemaCreateBegin();
ColumnSchema column_schema;
TableSchema table_schema = conn.createTable("INTERVENTIONS");

column_schema = table_schema.createColumn( "id", Domain.INTEGER );
column_schema.setNullable( false );

column_schema.setDefault( ColumnSchema.COLUMN_DEFAULT_GLOBAL_AUTOINC );

column_schema = table_schema.createColumn( "description",
Domain.VARCHAR, 512 );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "statut",
Domain.INTEGER);
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "duree",
Domain.INTEGER );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "idtechnicien",
Domain.INTEGER);
column_schema.setNullable( true );
...

IndexSchema index_schema =
table_schema.createPrimaryIndex( "primary" );
index_schema.addColumn( "id", IndexSchema.ASCENDING );
conn.schemaCreateComplete();

When I insert data into this table, I receive an exception :
ULjException: ianywhere.ultralitej.implementation.JrException:
UltraLiteJ Error[-195]: Column 'id' in table 'INTERVENTIONS' cannot be
NULL

2: We have the function getLastIdentity of interface connection in M-
business.
But We have not the equivalencie in UltralitJ, has anyone good
solution of getting the last identity ?


Reply With Quote
  #44  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 07:51 PM



There was a bug in the GA version that produced this problem, but it is
fixed and I do not see it in the EBF (11.0.0.1490). So either you have a
special case where there is still an issue or there is something else.

Have you seen this on device or in the emulator or both?

Sometimes I have had problems upgrading COD files on device and
emulator. On the emulator the best thing is to open a command prompt at
the \program files\research in motion\BlackBerry JDE <version>\simulator
directory and run "clean.bat" It takes several minutes to run, but it
does get rid of all installed COD files so that when you load a new one
you can be sure.

On device, it may be worth uninstalling UltraLiteJ and then adding the
new one, just to be sure again.

These procedures are not usually needed, but it seems there are some
times when just installing a new version doesn't overwrite the old version.

Tom Slee

GUO Lin wrote:
Quote:
It is about SQL UltraliteJ.

I have updated to the forth EBF release.
But I have still the problem about the function setDefault

1 : column_schema.setDefault( COLUMN_DEFAULT_GLOBAL_AUTOINC )

I define the table schema like this:

conn.schemaCreateBegin();
ColumnSchema column_schema;
TableSchema table_schema = conn.createTable("INTERVENTIONS");

column_schema = table_schema.createColumn( "id", Domain.INTEGER );
column_schema.setNullable( false );

column_schema.setDefault( ColumnSchema.COLUMN_DEFAULT_GLOBAL_AUTOINC );

column_schema = table_schema.createColumn( "description",
Domain.VARCHAR, 512 );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "statut",
Domain.INTEGER);
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "duree",
Domain.INTEGER );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "idtechnicien",
Domain.INTEGER);
column_schema.setNullable( true );
...

IndexSchema index_schema =
table_schema.createPrimaryIndex( "primary" );
index_schema.addColumn( "id", IndexSchema.ASCENDING );
conn.schemaCreateComplete();

When I insert data into this table, I receive an exception :
ULjException: ianywhere.ultralitej.implementation.JrException:
UltraLiteJ Error[-195]: Column 'id' in table 'INTERVENTIONS' cannot be
NULL

2: We have the function getLastIdentity of interface connection in M-
business.
But We have not the equivalencie in UltralitJ, has anyone good
solution of getting the last identity ?


Reply With Quote
  #45  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 07:51 PM



There was a bug in the GA version that produced this problem, but it is
fixed and I do not see it in the EBF (11.0.0.1490). So either you have a
special case where there is still an issue or there is something else.

Have you seen this on device or in the emulator or both?

Sometimes I have had problems upgrading COD files on device and
emulator. On the emulator the best thing is to open a command prompt at
the \program files\research in motion\BlackBerry JDE <version>\simulator
directory and run "clean.bat" It takes several minutes to run, but it
does get rid of all installed COD files so that when you load a new one
you can be sure.

On device, it may be worth uninstalling UltraLiteJ and then adding the
new one, just to be sure again.

These procedures are not usually needed, but it seems there are some
times when just installing a new version doesn't overwrite the old version.

Tom Slee

GUO Lin wrote:
Quote:
It is about SQL UltraliteJ.

I have updated to the forth EBF release.
But I have still the problem about the function setDefault

1 : column_schema.setDefault( COLUMN_DEFAULT_GLOBAL_AUTOINC )

I define the table schema like this:

conn.schemaCreateBegin();
ColumnSchema column_schema;
TableSchema table_schema = conn.createTable("INTERVENTIONS");

column_schema = table_schema.createColumn( "id", Domain.INTEGER );
column_schema.setNullable( false );

column_schema.setDefault( ColumnSchema.COLUMN_DEFAULT_GLOBAL_AUTOINC );

column_schema = table_schema.createColumn( "description",
Domain.VARCHAR, 512 );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "statut",
Domain.INTEGER);
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "duree",
Domain.INTEGER );
column_schema.setNullable( true );
column_schema = table_schema.createColumn( "idtechnicien",
Domain.INTEGER);
column_schema.setNullable( true );
...

IndexSchema index_schema =
table_schema.createPrimaryIndex( "primary" );
index_schema.addColumn( "id", IndexSchema.ASCENDING );
conn.schemaCreateComplete();

When I insert data into this table, I receive an exception :
ULjException: ianywhere.ultralitej.implementation.JrException:
UltraLiteJ Error[-195]: Column 'id' in table 'INTERVENTIONS' cannot be
NULL

2: We have the function getLastIdentity of interface connection in M-
business.
But We have not the equivalencie in UltralitJ, has anyone good
solution of getting the last identity ?


Reply With Quote
  #46  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 08:43 PM



One other question for you, Guo Lin. Have you set a database ID in the
database before using the global default autoincrement?
(see
http://dcx.sybase.com/1100en/ulj_en1...979537808.html)

Tom

Nick Elson [Sybase iAnywhere] wrote:
Quote:
I don't see any trace of this report as an open action item
but if this is a production affecting issue for you the
most affective approach is to work directly with the
support organization to assign priorities to engineering
resources to address any bugs here.

"GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message
news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com...
Hi, Nick

I read the document many time.
In fact, I found and reported the bug to Tom slee that
ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the
base in last release.

And I thought that you would fix the bug about ColumnSchema
( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ).

Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC.
I tested it in the forth EBF release. It does not work. You can see
the trace in the first article.
So I pose this problem here.

Lin








r


Reply With Quote
  #47  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 08:43 PM



One other question for you, Guo Lin. Have you set a database ID in the
database before using the global default autoincrement?
(see
http://dcx.sybase.com/1100en/ulj_en1...979537808.html)

Tom

Nick Elson [Sybase iAnywhere] wrote:
Quote:
I don't see any trace of this report as an open action item
but if this is a production affecting issue for you the
most affective approach is to work directly with the
support organization to assign priorities to engineering
resources to address any bugs here.

"GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message
news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com...
Hi, Nick

I read the document many time.
In fact, I found and reported the bug to Tom slee that
ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the
base in last release.

And I thought that you would fix the bug about ColumnSchema
( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ).

Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC.
I tested it in the forth EBF release. It does not work. You can see
the trace in the first article.
So I pose this problem here.

Lin








r


Reply With Quote
  #48  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 08:43 PM



One other question for you, Guo Lin. Have you set a database ID in the
database before using the global default autoincrement?
(see
http://dcx.sybase.com/1100en/ulj_en1...979537808.html)

Tom

Nick Elson [Sybase iAnywhere] wrote:
Quote:
I don't see any trace of this report as an open action item
but if this is a production affecting issue for you the
most affective approach is to work directly with the
support organization to assign priorities to engineering
resources to address any bugs here.

"GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message
news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com...
Hi, Nick

I read the document many time.
In fact, I found and reported the bug to Tom slee that
ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the
base in last release.

And I thought that you would fix the bug about ColumnSchema
( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ).

Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC.
I tested it in the forth EBF release. It does not work. You can see
the trace in the first article.
So I pose this problem here.

Lin








r


Reply With Quote
  #49  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 08:43 PM



One other question for you, Guo Lin. Have you set a database ID in the
database before using the global default autoincrement?
(see
http://dcx.sybase.com/1100en/ulj_en1...979537808.html)

Tom

Nick Elson [Sybase iAnywhere] wrote:
Quote:
I don't see any trace of this report as an open action item
but if this is a production affecting issue for you the
most affective approach is to work directly with the
support organization to assign priorities to engineering
resources to address any bugs here.

"GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message
news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com...
Hi, Nick

I read the document many time.
In fact, I found and reported the bug to Tom slee that
ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the
base in last release.

And I thought that you would fix the bug about ColumnSchema
( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ).

Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC.
I tested it in the forth EBF release. It does not work. You can see
the trace in the first article.
So I pose this problem here.

Lin








r


Reply With Quote
  #50  
Old   
Tom Slee
 
Posts: n/a

Default Re: column_schema.setDefault problem - 10-21-2008 , 08:43 PM






One other question for you, Guo Lin. Have you set a database ID in the
database before using the global default autoincrement?
(see
http://dcx.sybase.com/1100en/ulj_en1...979537808.html)

Tom

Nick Elson [Sybase iAnywhere] wrote:
Quote:
I don't see any trace of this report as an open action item
but if this is a production affecting issue for you the
most affective approach is to work directly with the
support organization to assign priorities to engineering
resources to address any bugs here.

"GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message
news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com...
Hi, Nick

I read the document many time.
In fact, I found and reported the bug to Tom slee that
ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the
base in last release.

And I thought that you would fix the bug about ColumnSchema
( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ).

Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC.
I tested it in the forth EBF release. It does not work. You can see
the trace in the first article.
So I pose this problem here.

Lin








r


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.