fsg
172da988ef
increment build number
2008-12-13 19:38:34 +00:00
fsg
9479a734b3
nightly update
2008-12-13 19:38:33 +00:00
asfernandes
de49fad692
increment build number
2008-12-13 18:25:46 +00:00
asfernandes
4769d47fa3
Fixed CORE-2237 - Assertion at src\jrd\intl.cpp 569
2008-12-13 18:25:45 +00:00
asfernandes
7a185c8bb4
increment build number
2008-12-13 17:46:06 +00:00
asfernandes
6f4886b9cf
Fix syntax error
2008-12-13 17:46:05 +00:00
robocop
4f99b06993
increment build number
2008-12-13 09:41:37 +00:00
robocop
8b20c40bf3
Misc.
2008-12-13 09:41:36 +00:00
robocop
d68bf80414
increment build number
2008-12-13 09:26:02 +00:00
robocop
548dfbd6b0
increment build number
2008-12-13 09:26:01 +00:00
robocop
761f0348ea
Style.
2008-12-13 09:26:00 +00:00
robocop
1297678c30
increment build number
2008-12-13 09:19:57 +00:00
robocop
030568068b
increment build number
2008-12-13 09:19:56 +00:00
robocop
38bd660bb2
Style, assertions and some minor fixed. To be reviewed by Dmitry.
2008-12-13 09:19:55 +00:00
robocop
8ab52cc3d4
increment build number
2008-12-13 09:19:24 +00:00
robocop
d18166f1bd
increment build number
2008-12-13 09:19:23 +00:00
robocop
f140cbb7d2
Before I put the "explicit" modifier on AtomicCounter's constructor, the compiler was generating a temporary AtomicCounter on the fly and later assigning it to the target AtomicCounter instance to satisfy an assignment of an integer to an AtomicCounter. I'm not sure we want to allow (and worse, foster) the copying of AtomicCounter instances or temporaries created by the compiler, hence I implemented a new method and fixed the code, but I don't know how to write the best code for one group of platforms in fb_atomic.h, hence I wrote the method with a syntax problem to be caught by someone who knows better.
2008-12-13 09:19:22 +00:00
fsg
355d4e9942
increment build number
2008-12-12 19:39:30 +00:00
fsg
0b758914bf
nightly update
2008-12-12 19:39:29 +00:00
alexpeshkoff
4914cfec86
increment build number
2008-12-12 16:52:52 +00:00
dimitr
f5e27dd239
increment build number
2008-12-12 16:04:58 +00:00
dimitr
40d041d628
Fixed the issue reported by Philippe. To be backported after more testing.
2008-12-12 16:04:57 +00:00
alexpeshkoff
8f7e64b9ab
increment build number
2008-12-12 14:16:07 +00:00
alexpeshkoff
aaaf28510a
Misc - thanks to Philippe
2008-12-12 14:16:06 +00:00
alexpeshkoff
5c69c449c5
increment build number
2008-12-12 13:53:13 +00:00
alexpeshkoff
e05841ead4
increment build number
2008-12-12 13:53:12 +00:00
alexpeshkoff
9377196fb7
increment build number
2008-12-12 13:53:11 +00:00
alexpeshkoff
817a8747a7
HPUX port
2008-12-12 13:53:10 +00:00
alexpeshkoff
e2945cd647
increment build number
2008-12-12 13:53:09 +00:00
alexpeshkoff
048e4c6f9f
increment build number
2008-12-12 13:28:37 +00:00
alexpeshkoff
c1762c9128
increment build number
2008-12-12 13:28:36 +00:00
alexpeshkoff
e160193f3e
increment build number
2008-12-12 13:28:35 +00:00
dimitr
20d649668d
increment build number
2008-12-12 11:24:47 +00:00
hvlad
dc4bd10b09
increment build number
2008-12-12 10:06:34 +00:00
hvlad
caac0ca6f3
increment build number
2008-12-12 10:06:33 +00:00
hvlad
a93f6c32f0
Some thread safety
2008-12-12 10:06:32 +00:00
dimitr
e58d227427
increment build number
2008-12-12 06:44:41 +00:00
dimitr
6405c3ab3c
increment build number
2008-12-12 06:44:25 +00:00
asfernandes
deddb81ed5
increment build number
2008-12-12 00:55:06 +00:00
asfernandes
b7a125c9e4
increment build number
2008-12-12 00:55:05 +00:00
asfernandes
5180f9c34b
increment build number
2008-12-12 00:55:04 +00:00
asfernandes
05947b7afc
Misc
2008-12-12 00:55:03 +00:00
asfernandes
dbdb835cb9
increment build number
2008-12-12 00:55:02 +00:00
asfernandes
c4360e713e
increment build number
2008-12-12 00:55:01 +00:00
asfernandes
8b765909f0
increment build number
2008-12-12 00:55:00 +00:00
asfernandes
c91a17ab83
increment build number
2008-12-12 00:54:59 +00:00
fsg
9f23c86b15
increment build number
2008-12-11 19:38:43 +00:00
fsg
d0e9d7736a
nightly update
2008-12-11 19:38:42 +00:00
dimitr
e64219e660
increment build number
2008-12-11 11:58:51 +00:00
dimitr
25dc79dce2
Fixed CORE-2209: Very slow procesing of the monitoring requests under high load and blocking other activity during that time.
...
The new code is expected to work 100-200 times faster. To be field-tested.
Implemented CORE-2233: Allow non-SYSDBA users to monitor not only their current attachment but other their attachments as well.
Sorry for mixing two fixes inside a single commit, but they're somewhat related.
2008-12-11 11:58:50 +00:00