Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Problem while using jConnect (TM) for JDBC(TM)/5.5(Build 25165) with sybase ASA 9.0

2 posts in General Discussion Last posting was on 2004-08-13 10:00:26.0Z
Nissamudeen Abdulsalam Rawther Posted on 2004-08-13 05:39:08.0Z
Reply-To: "Nissamudeen Abdulsalam Rawther" <rnissam@proactivenet.co.in>
From: "Nissamudeen Abdulsalam Rawther" <rnissam@proactivenet.co.in>
Newsgroups: ianywhere.public.general
Subject: Problem while using jConnect (TM) for JDBC(TM)/5.5(Build 25165) with sybase ASA 9.0
Lines: 12
Organization: Proactive Net Software
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4927.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
NNTP-Posting-Host: 203.200.51.98
X-Original-NNTP-Posting-Host: 203.200.51.98
Message-ID: <411c53fc@forums-1-dub>
Date: 12 Aug 2004 22:39:08 -0700
X-Trace: forums-1-dub 1092375548 203.200.51.98 (12 Aug 2004 22:39:08 -0700)
X-Original-Trace: 12 Aug 2004 22:39:08 -0700, 203.200.51.98
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3385
Article PK: 7293

hi
While creating tables without specifying the NOT NULL option for the column
name , default it taken as NOT NULL.

pls update...

rgds
nissam


Breck Carter [TeamSybase] Posted on 2004-08-13 10:00:26.0Z
From: "Breck Carter [TeamSybase]" <NOSPAM__bcarter@risingroad.com>
Newsgroups: ianywhere.public.general
Subject: Re: Problem while using jConnect (TM) for JDBC(TM)/5.5(Build 25165) with sybase ASA 9.0
Organization: RisingRoad Professional Services
Reply-To: NOSPAM__bcarter@risingroad.com
Message-ID: <ka3ph09fr22vee9njccrc1pdv7074459hr@4ax.com>
References: <411c53fc@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.640
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: adsl-223-217-221.mia.bellsouth.net
X-Original-NNTP-Posting-Host: adsl-223-217-221.mia.bellsouth.net
Date: 13 Aug 2004 03:00:26 -0700
X-Trace: forums-1-dub 1092391226 68.223.217.221 (13 Aug 2004 03:00:26 -0700)
X-Original-Trace: 13 Aug 2004 03:00:26 -0700, adsl-223-217-221.mia.bellsouth.net
Lines: 44
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3386
Article PK: 7290

The LOGIN_PROCEDURE option specifies which stored procedure will be
called when a new connection is made.

The default is sp_login_environment, which in turns calls
sp_tsql_environment for a JDBC connection.

That procedure contains this statement:

set temporary option Allow_nulls_by_default = 'OFF';

which accounts for the irritating behaviour you have experienced.

You can change this behaviour by writing your own stored procedure
which does *not* do anything, and change the LOGIN_PROCEDURE option:

SET OPTION PUBLIC.LOGIN_PROCEDURE = 'sp_do_nothing';

Breck

PS I am not sure if connections made with the new, better iAnywhere
JDBC driver behave differently... can anybody fill in? BC


On 12 Aug 2004 22:39:08 -0700, "Nissamudeen Abdulsalam Rawther"

<rnissam@proactivenet.co.in> wrote:

>hi
>While creating tables without specifying the NOT NULL option for the column
>name , default it taken as NOT NULL.
>
>pls update...
>
>rgds
>nissam
>
>
>

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/ASIN/1556225067/risingroad-20
bcarter@risingroad.com
Mobile and Distributed Enterprise Database Applications
www.risingroad.com