I've just raised a JIRA to track this...

http://issues.apache.org/activemq/browse/AMQ-1204

and have commited a patch using "DECIMAL" as the long integer and using the
SQL statement "LOCK TABLE foo IN EXCLUSIVE MODE" for the exclusive lock.

Do you want to try tomorrow's 4.2-SNAPSHOT build to see if this works?


On 3/14/07, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:

 For a large integer you can use the numeric data type.
Per the Sybase ASE documentation for ASE 12.5:

http://manuals.sybase.com/onlinebooks/group-as/asg1250e/sqlug/@Generic__BookTextView/15426;pt=15426#X


*Datatypes* by category

Synonyms

Range

Bytes of storage

*Exact numeric: integers*

tinyint

 0 to 255 (Negative numbers are not permitted.)

1

smallint

 215 -1 (32,767) to -215 (-32,768)

2

int

integer

231 -1 (2,147,483,647) to -231 (-2,147,483,648

4

*Exact numeric: decimals*

numeric (p, s)

 1038 -1 to -1038

2 to 17



As far as locking goes I think you want to use HOLDLOCK. This would be
specified after the table name and not at the end of the select statement.
It changes the isolation level of the transaction to level 3 (serializable).


http://manuals.sybase.com/onlinebooks/group-as/asg1250e/sqlug/@Generic__BookTextView/53713;pt=53713#X

Thanks for the help on this.

 ------------------------------
*From:* "James Strachan" <[EMAIL PROTECTED]> [mailto:"James
Strachan" <[EMAIL PROTECTED]>]
*Sent:* Wednesday, March 14, 2007 1:32 AM
*To:* users@activemq.apache.org
*Subject:* Re: ActiveMQ with Sybase for persistence

On 3/14/07, [EMAIL PROTECTED]
wrote:
> I've been trying to get this to work still and I now see an exception
> pertaining to BIGINT. It appears that Sybase ASE only began support for
> BIGINT in version 15. I'm stuck on 12.0.0.8. Any suggestions as to a
> workaround for this? Also I searched through the documentation on ASE 15
but
> found nothing pertaining to XLOCK. Am I missing something here?

Any idea what the correct SQL is for the following on Sybase 12.x

* creating an exclusive row/table lock
* a large integer column

Then we can create a JDBC adapter to handle your db
--

James
-------
http://radio.weblogs.com/0112098/




--

James
-------
http://radio.weblogs.com/0112098/

Reply via email to