26.07.2011 16:46, Alessandro Fiorino wrote:
Already tried it says it can't recover anything. Also tried ibrecovery
and it only recovers 20% of the data, less that what I have from my
last backup.
The IBSurgeon team also offers manual database recovery and they're
experienced in that. Perhaps
All,
I've faced problems while adding subj into trunk.
For procedure parameters, the syntax is:
COMMENT ON PARAMETER proc name.param name IS text
However, procedures and functions have different namespaces, so there
may be a function and its input parameter with exactly the same names.
Thus
I'm now convincing myself to the third option:
Extend the syntax but preserve backward compatibility via default:
COMMENT ON [{PROCEDURE | FUNCTION}] PARAMETER ...
but if the object type specifier is omitted, then the engine tries to be
smart and determine whether it's a procedure or a
05.07.2011 21:32, Paul Reeves wrote:
Are you running SuperServer, Classic or SuperClassic?
It is super server, although this should not make any difference.
Classic doesn't have any background I/O activity, so there will be a
difference.
Dmitry
05.07.2011 10:23, Paul Reeves wrote:
All tests are run from a freshly restored backup containing 100,000 rows in
the test table. Forced Writes are ON and hard drive disc caches are disabled.
Firebird 2.1.4 is the server.
FW and HDD settings don't affect the page I/O stats.
The attachment
29.06.2011 19:12, Paul Reeves wrote:
I've been studying the output of the MON$IO_STATS table but something doesn't
make sense. I've built a test rig that
a) catches the mon$io_stats to disk at the attachment level on disconnect
and
b) modifies a million records randomly during a
: Engine
Affects Versions: 2.5.0, 3.0 Initial
Reporter: Dmitry Yemanov
Test case:
create view v (id) as
select rdb$relation_id from rdb$database;
commit;
create procedure p as
declare id int;
begin
for select 1 from v into :id do begin end
end
commit;
execute procedure p
13.05.2011 9:43, Russell R wrote:
This post is related to the following 2 reported incidents:
http://tracker.firebirdsql.org/browse/CORE-3121
http://firebird.1100200.n4.nabble.com/Error-Restoring-v2-1-Database-to-v2-5-td2994314.html
The error is caused when you are running a 2.5 server, but
Components: Engine
Affects Versions: 2.1.4, 2.5.0, 2.0.6, 3.0 Initial, 2.1.3, 2.1.2, 2.0.5,
2.1.1, 2.0.4, 2.1.0
Reporter: Dmitry Yemanov
Priority: Minor
ISQL:
set planonly;
set sqlda_display;
select (null as int) from rdb$database;
-- sqltype = 497 (nullable
Affects Versions: 2.1.4, 2.5.0, 3.0 Initial, 2.1.3, 2.1.2, 2.1.1, 2.1.0
Reporter: Dmitry Yemanov
Test case:
SELECT LIST(F, '')
FROM (
SELECT CAST(ASCII_CHAR(0XFF) AS BLOB SUB_TYPE 0) AS F
FROM RDB$DATABASE
UNION ALL
SELECT CAST(ASCII_CHAR(0XDE) AS BLOB SUB_TYPE 0) AS F
09.05.2011 14:06, Vlad Khorsun wrote:
All metadata objects moved into Attachment. Metadata syncronization is guarded
by attachment's mutex now. Database::SyncGuard and company are replaced by
corresponding Attachment::XXX classes.
To make AST's work we need to release attachment mutex
05.05.2011 14:34, marius adrian popa wrote:
Feature request related to this thread
http://tech.groups.yahoo.com/group/firebird-support/message/113203
Maybe the api should show it somewhere like in the the engine_version
example http://firebirdsql.su/doku.php?id=rdb_get_context
SELECT
Type: Improvement
Components: Engine
Reporter: Dmitry Yemanov
Currently, the temp space manager is not tuned for small allocations properly.
This is so because historically it has been developed primarily for
sorting/merging purposes that are known to work with big memory
19.04.2011 9:49, Kovalenko Dmitry wrote:
Hi
The system table RDB$FUNCTION_ARGUMENTS (in ODS12) still exists
without RDB$DESCRIPTION field.
It was surely missed on my part, to be added.
RDB$PROCEDURE_PARAMETERS contains this (and RDB$SYSTEM_FLAG also) field.
I'm not so sure about
17.04.2011 22:03, Adriano dos Santos Fernandes wrote:
It's allowed to use XSQLVAR (or blr messages) between different types
like number-varchar (or vice-versa) but it's not allowed to use
different types when one of them is a blob.
DSQL moves data using MOVD_move, which do it like a client
17.04.2011 1:21, Leyne, Sean wrote:
Am I reading this correctly; any non-zero value would be considered true?
If so, then I do not agree with this logic. True values must be specific,
all other values must be false.
FWIW, this logic is used since v1.5 and nobody so far complained.
Dmitry
12.04.2011 2:09, Adriano dos Santos Fernandes wrote:
I suggest we fix namespace usages in an incremental manner. How?
[skip]
This way subsystems are children of Firebird namespace and don't require
Firebird:: everywhere. We also avoid using namespace Firebird in
implementation files.
It
13.04.2011 15:13, Alex Peshkoff wrote:
But, all things considered, I feel that the feature is too complicated
and has too many security implications to be worth it. If anything, I
might suggest that the alias config that's already present could be
augmented with a flag for each alias
11.04.2011 3:53, Adriano dos Santos Fernandes wrote:
Our functions dealing with XSQLDA/XSQLVAR has a dialect parameter.
When dialect is 0, the structures are interpreted as SQLDA/SQLVAR. These
structs are a legacy version with less items.
They declarations are not present in ibase.h at
02.04.2011 12:53, Thomas Steinmaurer wrote:
in respect to the sub-release policy, I guess that forthcoming V2.5
sub-releases also won't include new features. But, would it be
*technical* possible to add the Window functions to the V2.5 branch or
is there too much needed from the V3 code base?
01.04.2011 11:51, Dimitry Sibiryakov wrote:
I don't understand why this job is deferred. If DDL is impossible, user must
be informed
about this fact ASAP.
In order to perform the validation, you have to lock the table from
concurrent modifications. If it's done ASAP and the lock is then
01.04.2011 12:24, Alex Peshkoff wrote:
Dmitry, where have you found a reference in standard tat string column
can be altered to wider one type?
What Is see in SQL2008 is:
Your copy is outdated :-) My version of 2010-10-14 says:
alter table statement ::=
ALTER TABLE table name alter table
01.04.2011 12:53, Dimitry Sibiryakov wrote:
May I suggest to add non-standard optional clause NOVALIDATE for users who
are sure
that validation is unnecessary and want to save time on commit?..
I'm against this. But feel free to keep arguing :-)
Dmitry
1201 - 1223 of 1223 matches
Mail list logo
