[ 
https://issues.apache.org/jira/browse/DERBY-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804252#comment-13804252
 ] 

Knut Anders Hatlen commented on DERBY-6389:
-------------------------------------------

The example in the Error message differences topic is outdated. Now it produces 
the same output in both environments:

{noformat}
ij> create table ai (x int, y int generated always as identity (increment by 
200000000));
0 rows inserted/updated/deleted
ij> insert into ai (x) values (1),(2),(3),(4),(5),(6),(7), 
(8),(9),(10),(11),(12),(13),(14),(15),(16),(17),(18),(19);
ERROR 42Z24: Overflow occurred in identity value for column 'Y' in table 'AI'.
ERROR 22003: The resulting value is outside the range for the data type INTEGER.
{noformat}

We could probably remove the entire topic now.

> Update adminguide's list of differences between client and embedded
> -------------------------------------------------------------------
>
>                 Key: DERBY-6389
>                 URL: https://issues.apache.org/jira/browse/DERBY-6389
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>
> The admin guide has a chapter that describes known differences between the 
> client driver and the embedded driver: 
> http://db.apache.org/derby/docs/10.10/adminguide/cadminapps.html
> Most of this information was added for the original network client 
> implementation in 10.1 (DERBY-371) and has not been updated since.
> For example, 
> http://db.apache.org/derby/docs/10.10/adminguide/cadminappsclientdiffs.html 
> says SQLStates for exceptions on the client may be null. I believe this was 
> fixed in 10.2 as part of DERBY-254.
> It also says that SQLExceptions (and SQLWarnings) won't be chained, but that 
> was fixed in 10.3 (DERBY-2692). That outdated information is also repeated 
> here: http://db.apache.org/derby/docs/10.10/adminguide/radminapps811974.html



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to