DATEDIFF behavior bug
-
Key: CORE-3793
URL: http://tracker.firebirdsql.org/browse/CORE-3793
Project: Firebird Core
Issue Type: Bug
Affects Versions: 2.5.1
Environment: Windows 2008 Server R2
Repor
22.03.2012 10:52, Thomas Steinmaurer wrote:
>
> would it be possible to reactivate the Firebird 3 snapshot builds for
> Windows?
The fixed builds are being compiled at the moment and will be uploaded
shortly.
Dmitry
--
EXECUTE STATEMENT On EXTERNAL doesn't work for database files containing german
Umlaute äöüß
Key: CORE-3794
URL: http://tracker.firebirdsql.org/browse/CORE-3794
Hi all,
I've noticed that in Fb 3, the MECHANISM for procedure & function
parameters is set to "1", meaning "type of", even though you're using
raw datatypes.
An implicit domain is created automagically in RDB$FIELDS, but I
think that the mechanism should be 0 then, don't you?
With regards,
Ma
On 03/21/12 17:22, Thomas Steinmaurer wrote:
> Hello,
>
> it seems I can't install SC of Firebird 3.0 as a service.
>
> There is no appropriate .bat file for that. While I could create one or
> take the one from 2.5, instsvc.exe in the 3.0 snapshot is out-dated, at
> least according to the usage
> I've noticed that in Fb 3, the MECHANISM for procedure& function
> parameters is set to "1", meaning "type of", even though you're using
> raw datatypes.
>
> An implicit domain is created automagically in RDB$FIELDS, but I
> think that the mechanism should be 0 then, don't you?
Test case: ;-)
22.03.2012 12:06, Alex Peshkoff wrote:
> From command line switches POV there is no difference in FB3 between SS
> and SC - they both are 'single process serving multiple connections'.
> But if instsvc does not support -m, you can't install SS too.
You can, as it still has options "superserver" a
Hi Alex,
>> it seems I can't install SC of Firebird 3.0 as a service.
>>
>> There is no appropriate .bat file for that. While I could create one or
>> take the one from 2.5, instsvc.exe in the 3.0 snapshot is out-dated, at
>> least according to the usage information, as it doesn't support the
>> -
On 03/22/12 12:22, Dmitry Yemanov wrote:
> 22.03.2012 12:06, Alex Peshkoff wrote:
>
>> From command line switches POV there is no difference in FB3 between SS
>> and SC - they both are 'single process serving multiple connections'.
>> But if instsvc does not support -m, you can't install SS too.
>
22.03.2012 12:29, Thomas Steinmaurer wrote:
>
> => Does that mean: We have a single executable in Firebird 3. When -m is
> used, this means a single server process and the SharedCache,
> SharedDatabase parameters controll whether it's SS or SC. When -m is not
> used, then it's one process per conn
22.03.2012 12:34, Alex Peshkoff wrote:
> Probably small change in help text - SS or SC - will be useful.
Before doing that, we need to decide whether the former SuperClassic
will be the documented option or just some "internal" stuff for easier
debugging etc, as FB3 is intended to make it mostl
On 03/22/12 12:29, Thomas Steinmaurer wrote:
> => Does that mean: We have a single executable in Firebird 3. When -m is
> used, this means a single server process and the SharedCache,
> SharedDatabase parameters controll whether it's SS or SC. When -m is not
> used, then it's one process per co
>> => Does that mean: We have a single executable in Firebird 3. When -m is
>> used, this means a single server process and the SharedCache,
>> SharedDatabase parameters controll whether it's SS or SC. When -m is not
>> used, then it's one process per connection thus CS.
>>
>> Is this correct?
>
22.03.2012 13:00, Thomas Steinmaurer wrote:
> * Under the assumption that SS as a single-process model with it's
> shared cache supports SMP (I think this was a primarly goal) in 3.0 like
> SC in 2.5, I don't see a reason to offer SC in 3.0 at all (at least the
> SC terminology; which already show
Alex Peshkoff [2012-03-22 09:43] :
> BTW, in posix things are even more funny. "firebird" executable detects,
> is it started from shell (SS/SC) or from (x)inetd network listener (CS).
> Therefore no switch "-m" is needed at all.
and in that case, what about systemd, where xinetd is no longer
some
On 03/22/12 13:13, Dmitry Yemanov wrote:
> 22.03.2012 13:00, Thomas Steinmaurer wrote:
>
>> * Under the assumption that SS as a single-process model with it's
>> shared cache supports SMP (I think this was a primarly goal) in 3.0 like
>> SC in 2.5, I don't see a reason to offer SC in 3.0 at all (a
On 03/22/12 13:48, philippe makowski wrote:
> Alex Peshkoff [2012-03-22 09:43] :
>> BTW, in posix things are even more funny. "firebird" executable detects,
>> is it started from shell (SS/SC) or from (x)inetd network listener (CS).
>> Therefore no switch "-m" is needed at all.
> and in that case
Hello, All!
We completed (conditional) implementation of lock manager buffer > 2 GB and put
it into production.
The production system tends to be 100% CPU bound now (as there is a few days
back-log of work).
All 24 cores are busy, 450 GB RAM utilized for one database.
Roughly ~50% of CPU time
18 matches
Mail list logo
