09.03.2014 12:00, Claudio Valderrama C. wrote:
Ok, as I said, this restriction already exists, but the message is not good.
Unlike Ann, I'm not a debugging wizard, but because I couldn't make sense of
it by reading the sources, I had to call VS and found that an ACL is corrupt
when walk_acl()
/browse/CORE-4356
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 2.1.4, 2.5.0, 2.1.3, 2.1.2, 2.1.1, 2.1.0
Reporter: Dmitry Yemanov
Artificial test case:
set term ^;
execute block as
declare stt varchar(255) = 'execute
03.03.2014 20:57, Alex Peshkoff wrote:
If we apply that change SQLDA-oriented functions can work with 64K
messages but BLR-oriented statements and requests - can not.
Fortunatelly, I don't know anybody who use them.
Anyone who is using gpre.
If we speak about indirect usage, could gbak
03.03.2014 21:54, Dimitry Sibiryakov wrote:
Its result set cannot be wider than record, which is still limited to 64k, so
no
problem here.
We can allow records longer than 64K in a second. The only reason why it
was not done yet is the old API problem in gbak. I hope Alex will
rewrite the
28.02.2014 22:06, Adriano dos Santos Fernandes wrote:
Isn't it related to the READ/WRITE BLOB commands, which was removed from v3?
It looks so. Blob errors could be priorly returned from DSQL API calls
only in case of these commands, but now this should not happen.
Dmitry
Affects Versions: 3.0 Alpha 2, 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1,
2.5.2, 2.1.5, 2.5.1, 2.1.4, 2.5.0, 2.1.3, 2.1.2, 2.1.1, 2.1.0
Reporter: Dmitry Yemanov
Priority: Minor
In external sorting (SORT plan), every record being sorted is stored as the
sort key plus all
Claudio,
Nice, although some of them seem to be false alarms. For example,
TextType::compare(). The typical result is -1, 0, 1. I would prefer to
change the result to plain int, but it may not be possible (I would have to
check all places affected).
The problem here may be theoretical rather
19.02.2014 19:19, Adriano dos Santos Fernandes wrote:
One thing of ICU we use and allows the user to use with CREATE COLLATION
is the Unicode localization table variants (per country).
We used to strip almost everything and add the variants we used in ours
builtin collations. User left with
Components: GBAK
Affects Versions: 3.0 Alpha 2, 3.0 Alpha 1
Reporter: Dmitry Yemanov
Restore ends with error:
gbak: ERROR:invalid request BLR at offset 201
gbak: ERROR:generator RDB$GENERATOR_NAME is not defined
gbak:Exiting before completion due to errors
--
This message
Adriano,
It seems that Windows people decided that a multi-megabyte library
should not be included in Firebird.
IIRC, the ICU site had an ability to generate stripped libs online. Is
that still possible? We might use that for officially distributed
packages and let people dealing with
15.02.2014 13:25, liviusliv...@poczta.onet.pl wrote:
Your explanation is very good but i see that i was not clear in question.
I understand that collate is for sorting or upper but what is difference
in maining of collation in this three queries.
What do
Select field collate pxw_plk from ...
Adriano,
ICU 5.2 comes only with MSVC 10 build. It should not be possible for
us to create solution for older MSVC.
Are we prepared for this?
Sorry, I don't get why it should not be possible for us? Our official
compiler for v3 is MSVC10 -- so far so good -- but if someone still
wants to
Adriano,
With older ICU, you probably used Visual Studio to upgrade older format
to newer one.
Now, the inverse will be necessary. AFAIK, Nickolay used something for
this, but I don't know if it was fully functional or needed manual edits.
But note, ICU has not only vcxproj files. It has
14.02.2014 21:16, Adriano dos Santos Fernandes wrote:
Why to compile ICU by hands at all? What's wrong with precompiled binaries?
That is a interesting question.
Would need to choose if include binaries in the repository or not.
If not, build will not be simple and may need extra download.
14.02.2014 22:50, Thomas Steinmaurer wrote:
Would like to do so, but the latest snapshot build for Windows available
is from 2 days ago. Just letting you know.
Windows builds are broken at the moment, please wait a bit.
Dmitry
13.02.2014 12:23, Vlad Khorsun wrote:
Good point. I think it makes sense. I'll look at it (a bit later). Would you
like to
see procedure name prefixed with package name (PACKAGE.PROCEDURE)
This would be consistent with the rest of the codebase, so IMHO it
should be done this way.
Dmitry
13.02.2014 19:39, Dimitry Sibiryakov wrote:
As I wrote in ticket: fbclient.dll installed into system directory produces
unreadable
error messages because of absence firebird.msg nearby.
Do you mean really unreadable or actually readable but prefixed with
cannot locate firebird.msg? Example
Claudio,
Hello, while trying to run the full compilation for FB3, I got
Assertion (!bestCandidate-condition) failure:
...\..\..\src\jrd\Optimizer.cpp 1576
just when isql started running in the make_boot process. I'm not sure about
the committer's name but it seems it ends with y.
He knows
03.02.2014 21:21, marius adrian popa wrote:
With fresh Firebird 3.0 install i have with flamerobin (even if i
enable legacy auth and flamerobin is loading the new fbclient)
Why do you need legacy auth if you use the new client? And how exactly
did you enable it?
Dmitry
29.01.2014 21:30, Leyne, Sean wrote:
OK, but some of the config options are not compatible for all installed modes
-- so, how do we prevent a user make the wrong selections?
If someone like Paul Reeves (who has been using FB since before it was FB)
doesn't understand all of the
30.01.2014 13:43, Vlad Khorsun wrote:
Technically it is possible to make single instance of firebird.exe to handle
some attachment requests by forking new CS process and another attachment
requests handling by itself (SS\SC).
Do you mean forking the worker after op_connect / op_attach are
29.01.2014 18:37, Paul Reeves wrote:
I guess what we really need is to document in firebird.conf how the -m switch
affects the other two settings. There would seem to be a total of eight
combinations.
Lack of -m switch along with SharedDatabase = false means that only the
first connection
29.01.2014 20:51, Paul Reeves wrote:
# SharedCache SharedDatabase -m Mode
# false false *
SC single attach only
Interesting. Does that differ internally from
# truefalse - ?
SS single attach only
Mostly it doesn't, except the fact that
29.01.2014 21:07, Dimitry Sibiryakov wrote:
How about difference latch only vs latch+lock? Does it still exist in v3?
Page locks are not used until the second connection appears. And other
lock types don't affect single-threaded performance.
Dmitry
29.01.2014 21:10, Leyne, Sean wrote:
EngineMode/EngineType = Classic | SuperServer | SuperClassic
DatabaseAccess = Shared | Single
The install options should take their cue from the config settings, and not
require inline switches.
Config options are database wise, so using them at the
25.01.2014 18:22, Adriano dos Santos Fernandes wrote:
Adding some keyword for now may cause future problems when schemas exist.
What's the problem of treating ::PROC1 (syntax just for example) as a
global procedure PROC1 in the current schema? Or do you mean the
situation when multiple
26.01.2014 00:56, Helen Borrie wrote:
However current situation should be reflected in Release Notes.
From a design perspective, my simple-minded view is that homonymity of the
kind that leads to conflicts within the scope of the current_schema should be
avoided. You seem to be saying
21.01.2014 21:34, Leyne, Sean wrote:
This seems to be an item which should really be discussed in the Support
mailing list (http://groups.yahoo.com/group/firebird-support/), not here in
the core developers lists.
FB3 issues do belong here, not the support list.
Dmitry
17.01.2014 19:16, Adriano dos Santos Fernandes wrote:
I think IUtl::version
Being there, please rename it to getVersion(). As usual, I'm strongly
against nouns used as routine names.
Also I think IUtl::edit should not exist. It's a too specialized ISQL
feature, and IMO should be there in
08.01.2014 12:15, Kjell Rilbe wrote:
That said, I'd vote against plan for/hint if the plan clause in its
current use is or is soon going to be deprecated. So, what are the plans
for the plan clause?
Explicit planning is still used by some customers, so it cannot be
deprecated. But it's not
Ann,
The FIRST keyword was added to Firebird's SQL in version 1.0 or 1.1 -
in 2000 0r 2001, but the use of FIRST in InterBase goes back much further.
It was part of GDML - and it's purpose was to signal that the query should
be optimized to walk the index (navigate, in the internals) rather
07.01.2014 12:28, Alex wrote:
Or even config file option. Not related with SQL IMHO.
It *is* related as soon as you need to alter from the default FIRST ROWS
to custom FIRST ROWS in some particular query.
Dmitry
--
07.01.2014 12:46, Dmitry Yemanov wrote:
It *is* related as soon as you need to alter from the default FIRST ROWS
to custom FIRST ROWS in some particular query.
Read: custom ALL ROWS, sorry.
Dmitry
--
Rapidly
07.01.2014 13:25, Simonov Denis пишет:
Strategy ALL ROWS default optimizer I consider correct. Nevertheless, I
believe that it is necessary to introduce a parameter in the configuration
database level which could be returned to the old behavior where the
optimizer to use a strategy FIRST
Kjell,
This makes sense, but I also think what Jim Starkey said makes sense,
i.e. that introducing optimizer hints in essence means you've given up
on creating a good automatic optimizer.
Jim is not alone in thinking this way. This is why I explicitly
mentioned that I don't want to discuss
08.01.2014 00:49, Mark Rotteveel wrote:
I do think you should consider the implications of having full featured
hints in the future, if only not to make a poor choice now when it comes
to syntax.
And I suggested how the OPTIMIZE clause can be extended later, if required.
Dmitry
08.01.2014 10:30, liviusliv...@poczta.onet.pl wrote:
Why plan can not by extended for hint purposes?
It can, the question is whether it should.
This is natural placefor FB users to tell optimizer
the better way of query execution.
Personally, I see an important difference between planning
Ann,
Right. And if you want to give the optimizer a hint that it should choose
the second plan, change the query like this:
select first 100 * from MOVIES where COMMENTS like '%yacht% order
by NAME;
If you think your client may want more than a million rows, increase
that number.
I
Martijn,
is a privilege “G” in RDB$USER_PRIVILEGES actually a granted “Usage”?
Yes, it stands for usaGe :-) for the lack of better one-letter
representation.
Per standard, it also applies to exceptions, domains, charsets,
collations. However, the engine validates it only for sequences and
://tracker.firebirdsql.org/browse/CORE-4313
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0 Alpha 1, 3.0 Alpha 2
Reporter: Dmitry Yemanov
Call sequence that demonstrates the issue:
isc_dsql_allocate_statement(status, db, st
All,
We had this topic raising from time to time, resulted in CORE-1488. So
far there was no appropriate discussion and hence no decision made,
although one might argue that the optimizer should be clever enough to
make hints unnecessary. The PGSQL guys share the same opinion, BTW ;-)
As for
02.01.2014 21:43, Mark Rotteveel wrote:
It would be interesting to know which is better for performance, given
isc_dsql_fetch, a FIRST (x) ROWS might perform better when small fetch
sizes are used.
What do you mean by small fetch sizes? If it's about incomplete fetch,
i.e. only few rows are
29.12.2013 11:46, Norbert wrote:
yes everything by default and then I changed to try if it changed
something but nothing nothing!
Where did you get binaries?
http://web.firebirdsql.org/download/snapshot_builds/win/3.0/
Did you try with ISQL from this package or with other software?
16.12.2013 14:38, Simonov Denis wrote:
Will the new name-value pairs also be retrievable from sec$users? And if
yes, how ? Text blob with all pairs?
It was nice to have some system stored procedure parses BLOB and returns a
set of keys and values
Wouldn't a table e.g. SEC$USER_ATTRIBUTES be
10.12.2013 12:28, Philippe Makowski wrote:
Under 3.0 we get a :
Statement failed, SQLSTATE = 42S22
Dynamic SQL Error
-SQL error code = -206
-Column unknown
-TR.ID_TYPE_PRODUCT
-At line 25, column 26
Fixed now.
Dmitry
10.12.2013 12:28, Philippe Makowski wrote:
Under 3.0 we get a :
Statement failed, SQLSTATE = 42S22
Dynamic SQL Error
-SQL error code = -206
-Column unknown
-TR.ID_TYPE_PRODUCT
-At line 25, column 26
I will take a look, thanks.
Dmitry
03.12.2013 15:10, liviusliv...@poczta.onet.pl wrote:
All projects which use integer in designer faill becouse of that.
I'm wondering what connectivity layer do you refer to and what error it
raises. I don't see why it should fail provided that the returned value
does not overflow the 2^32
03.12.2013 21:09, Dimitry Sibiryakov wrote:
It won't help. If in Delphi db-aware components fields were created in design
time and
this field was created with type ftInteger, there is no way FB API can find
it out and
report ISC_LONG instead of ISC_INT64.
Doesn't it mean that such an
Reporter: Dmitry Yemanov
Currently, when ORDER plan is in game, the optimizer chooses the first index
candidate that matches the ORDER BY / GROUP BY clause. This is not the best
approach when multiple index choices are available, see examples below.
create table test (col1 int, col2 int
24.11.2013 23:21, Mark Rotteveel wrote:
I assume that is an artifact of the implementation, could you point me
to some code that shows this. If I look at the (wire!) protocol itself,
there is no such limitation to the total message length when sending
parameters (eg in op_execute2), although
15.11.2013 12:46, Alex Peshkoff wrote:
Warning: this commit changed ODS, therefore old databases have
bugcheck(183).
Adriano, I've thought that for missing fields we get NULL value, not
bugcheck? That's not dangerous at alpha stage, but may be I've missed
something? Were you going to make
Versions: 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2,
2.1.5, 2.5.1, 2.1.4, 2.5.0, 3.0 Initial, 2.1.3, 2.1.2, 2.1.1, 2.1.0
Reporter: Dmitry Yemanov
The server process may crash during the sweep under some conditions. They are:
- nobody accessed the problematic tables before
: Engine
Affects Versions: 3.0 Alpha 1, 3.0 Initial
Reporter: Dmitry Yemanov
Races are possible between listener and worker threads when a database is being
disconnected (op_exit / op_disconnect packets are processed), sometimes causing
the remote server to crash. So far
15.11.2013 11:29, Philippe Makowski wrote:
seems that some of lasts commits broke something
http://ci.ibphoenix.com/
Am I right in detecting the reason as:
# Your password can be changed to a more suitable one using the
# /opt/firebird/bin/gsec utility.
#
+ awk 'BEGIN { FS = = } ; { print $2
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0 Alpha 1, 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 2.1.5
Reporter: Dmitry Yemanov
Under high concurrent load isc_attach_database() may return isc_lock_conflict
error:
Statement
13.11.2013 11:10, liviuslivius wrote:
i suppose that changing integer value from 32764 to the same value as is in
Interbase will cause that FB and IB will be compatible for Boolean
but may by i am wrong - i know only a little about internals
Having the same SQL-types means that both the
12.11.2013 22:11, Mark Rotteveel wrote:
Should I just file a bug?
Feel free, we can always reject it g
Do you have a simple test case for this error? You said it was happening
in specific tests, so it should be reproducible.
Dmitry
10.11.2013 18:40, Mark Rotteveel wrote:
The test suite is 1288 tests at the moment (and I expect the number of
tests to increase further). For the majority of tests a database is
created and dropped per test! So contrary to normal users, performance
of create and drop is pretty important to
05.11.2013 14:56, Alex Peshkoff wrote:
This change seems to be absolutely safe no matter of what more
performance optimizations we will try later.
I'd also start with this solution first.
Dmitry
--
November
26.10.2013 13:29, Mark Rotteveel wrote:
I just noticed that roles are case sensitive when they are created
quoted, is that correct behavior?
It is. Roles are regular SQL identifiers.
Dmitry
--
October Webinars:
26.10.2013 14:30, Mark Rotteveel wrote:
Ok, then how do I need to add a case sensitive role to the dpb to get it
to work?
Put it there with quotes.
Dmitry
--
October Webinars: Code for Performance
Free Intel
26.10.2013 16:07, Mark Rotteveel wrote:
If I explicitly specify the connection dialect (isc_dpb_sql_dialect),
then it does work. I was under the assumption that if no explicit
dialect is specified, that Firebird uses dialect 3. Is that assumption
wrong?
It is wrong. No dialect passed means
26.10.2013 16:52, Dimitry Sibiryakov wrote:
How to find out what dialect to use for connection before connection?
The dialect is needed before connection only to process the role name
properly. And you DO know whether your role name is mixed-case before
connection. So the usage pattern is
Adriano,
Can anyone review the attached (in this message) patch?
The solution looks correct. However, it breaks CORE-3806. The condition
should be:
if (rpb-rpb_relation !rpb-rpb_number.isValid())
VIO_record(...);
See my related comment at the end of SortedStream::open().
BTW, once
09.10.2013 20:00, Adriano dos Santos Fernandes wrote:
ISQL is full of duplicate code to handle different ODS. And it's still
bug, requiring more and more copy-past-and-adjust code.
I agree this is a major PITA.
I propose we start in 3.0 to do this. Of course, ISQL from 3.0 will not
fully
10.10.2013 11:41, Alex Peshkoff wrote:
If (for example) when asked about list of packages it will show empty
one this will be _very_ good compromise.
New system tables still require conditional code, it's unlikely be
simplified. But Adriano's suggestion could work for 90% of other cases
(new
08.10.2013 18:39, Nick Upson wrote:
I'm trying to restrict the ports that fb can use for events to a small
range, I thought I needed to make changes to aux_request in
src/remote/inet.cpp but it seems I was wrong. could someone please point
me in the right direction.
This should be the
Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0 Alpha 1
Reporter: Dmitry Yemanov
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure
://tracker.firebirdsql.org/browse/CORE-4236
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0 Alpha 1
Environment: SuperServer only
Reporter: Dmitry Yemanov
Database shutdown procedure was reworked in v3 and v2.5.3 to be more
19.09.2013 13:39, Mark Rotteveel wrote:
While working on Jaybird I noticed that the implementation that requests
the execution plan (isc_info_sql_get_plan) skipped the first byte of the
String buffer (and the .net implementation does as well).
On closer examination it turns out that the plan
04.09.2013 11:43, Alex Peshkoff wrote:
May be in that case next step? Keep declaring strings as char(N), but
treat N not as maximum size of string
Please don't play against the SQL standard. The declared string length
is a constraint which must be enforced.
Dmitry
04.09.2013 23:34, Fabiano - Desenvolvimento SCI wrote:
Now I get another problem:
gbak:committing metadata
gbak: ERROR:invalid request BLR at offset 1769
gbak: ERROR: BLR syntax error: expected variable identifier at offset
1770, encountered 76
gbak: ERROR: Error while parsing
03.09.2013 11:13, Alex Peshkoff wrote:
That's definitely a candidate for next ODS. But I see one problem -
currently all (or at least most of all) record buffers are allocated at
prepare time. With variable record length this strategy requires change,
and that change does not look trivial at
01.09.2013 06:29, Ann Harrison wrote:
I think this is correct - if unexplicable - behavior according to the
Standard. Something about the state of the column prior to the operation.
I respectfully disagree. The NEW context is in the perfectly valid state
in the BEFORE INSERT triggers. If
27.08.2013 20:03, Adriano dos Santos Fernandes wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
Basically, I don't mind, but the behavior will be different from
constraints in regard to the already existing
22.08.2013 10:28, liviuslivius wrote:
i need to know what is in plan next after fb3 release and with what
priority.
We'll be happy to share this information once we have a roadmap for the
future versions. Before that, it will be just speculations. For the time
being, I'd rather prefer to
13.08.2013 11:55, Dimitry Sibiryakov wrote:
Because plans are read from bottom to the top, I would prefer something like
this:
(A)
Select Expression
- Aggregate
- Sort (unique)
- Table RDB$RELATIONS Access By ID
- Index RDB$INDEX_0 Scan
Now imagine two
All,
There are some kinds of queries that have data access methods linked to
each other. Windowed functions are the obvious example, but it happens
even for regular aggregate functions. For example, COUNT(DISTINCT) needs
not only read the underlying stream but also sort it in order to
Issue Type: Bug
Components: API / Client Library
Affects Versions: 3.0 Alpha 1
Reporter: Dmitry Yemanov
Instead of returning implementation details and keeing the old API weirdness,
let's provide a clear implementation in IMessageMetadata. Now, for SQL_BLOB
10.08.2013 21:20, liviuslivius пишет:
and i test this also against Oracle 11g
and try SELECT T.ID, row_Number() over() FROM TEST
i get error the same as in MSSQL
Error: ORA-30485: missing ORDER BY expression in the window specification
PGSQL 9.1:
postgres=# select id from test;
id
Type: Bug
Components: Engine
Affects Versions: 3.0 Alpha 1
Environment: Classic/SuperClassic (SharedDatabase = true)
Reporter: Dmitry Yemanov
When MON$ tables are queried the first time, only information for the current
connection is returned. If some other
06.08.2013 11:04, liviuslivius wrote:
if you need more info, please ask me
Can you provide the sample database?
Dmitry
--
Get your SQL database under version control now!
Version control is standard for application
05.08.2013 17:57, liviuslivius wrote:
Firebird 3.0
i have database backup file (from import server) and now i need to
restore it on production server
On import server external tables access is set Full
on Production Server it is Set to None
then when i try to restore database on Production
: http://tracker.firebirdsql.org/browse/CORE-4168
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0 Alpha 1
Reporter: Dmitry Yemanov
Engine Code : 335544831
Engine Message : Access to external file PLAYERS.EXT is denied
04.08.2013 16:47, Simonov Denis wrote:
select 1
from rdb$database
where true is true
Work is correct
select 1
from rdb$database
where (1=1) and true
Work is correct
select 1
from rdb$database
where (1=1) is true
Invalid token.
Dynamic SQL Error.
SQL error code = -104.
Components: Engine
Reporter: Dmitry Yemanov
Test case #1:
select 0 i from rdb$database
union all
select 1 from rdb$database
union all
select 2 from rdb$database
Current plan:
Select Expression
- Union
- Union
- Table RDB$DATABASE Full Scan
: 3.0 Alpha 1
Reporter: Dmitry Yemanov
Priority: Minor
Two issues are observed when looking at the reported memory statistics:
1) Page cache size is not included into the global (database wise) counters
2) OS allocation counters can be around ~4GB
So far I can confirm only
04.08.2013 11:20, Mark Rotteveel wrote:
Ok, lets not call it a bug, but an area of potential improvement: based
on the context it should be possible to deduce that the literal should
be a smallint. Therefor it should be possible to handle 0x8000 as -32768
when assigned to a smallint and as
03.08.2013 19:12, Mark Rotteveel wrote:
A test in Jaybird for warnings registered on a connection uses
isc_dpb_set_db_sql_dialect to change a dialect 3 database to 1.
In Firebird 2.5 and earlier this triggers a warning (Database dialect
being changed from 3 to 1, error code 335544802), in
page:
http://www.firebirdsql.org/en/firebird-3-0-0-alpha1/
Release Notes:
http://web.firebirdsql.org/download/prerelease/rlsnotes/Firebird-3.0.0_Alpha1-ReleaseNotes.pdf
--
Dmitry Yemanov
--
Get your SQL database under
31.07.2013 16:15, marius adrian popa wrote:
ipv6 support was merged in 3.0 ?
IIRC, not (yet).
Dmitry
--
Get your SQL database under version control now!
Version control is standard for application code, but
09.07.2013 18:35, Thomas Beckmann wrote:
I get this error
Statement failed, SQLSTATE = 2F000
sort record size of 187704 bytes is too big
-Error while parsing procedure PKG$.P_SOMEPROCEDURE's BLR
on recreating the package body.
It has nothing to do with the package/procedure size, it's
Components: Engine
Affects Versions: 3.0 Initial, 3.0 Alpha 1
Reporter: Dmitry Yemanov
Artificial test case:
select distinct rdb$relation_id + 0, rdb$relation_name
from rdb$relations
order by rdb$relation_name
--
This message is automatically generated by JIRA
Core
Issue Type: Bug
Components: Engine
Affects Versions: 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 2.1.5, 2.5.1,
2.1.4, 2.5.0, 2.1.3, 2.1.2, 2.1.1, 2.1.0
Reporter: Dmitry Yemanov
Test case:
create table A (ID int);
create table B (ID int);
create index IDX
Adriano,
v3:
b) If a connection charset is used, parameters are described with the
connection charset. This is wrong, NONE should continue as NONE.
Sorry, I don't get you here. If you're talking about implicit (omitted)
charset in parameters and connection charset is not NONE, where that
04.07.2013 16:13, Thomas Beckmann wrote:
Finally
gbak -b c:\temp\test.fdb c:\temp\test.fbk
gbak: ERROR:Unable to perform operation. You must be either SYSDBA or
owner of the database
gbak:Exiting before completion due to errors
I still am the owner of the database (I hope ;-))
gbak -b
01.07.2013 17:14, Pavel Cisar wrote:
Next issues were discovered via FDB test suite. Tested on 64-bit Linux,
default configuration (i.e. vanila install from tar.gz).
Were connections true local (embedded) or via localhost?
1. cursor.rowcount (isc_dsql_sql_info with isc_info_sql_records)
20.06.2013 10:50, Philippe Makowski wrote:
seems that 2.5 don't build
http://ci.ibphoenix.fr/job/firebird25_Linux_64/89/
Thanks. I've committed a workaround, but cannot validate it. Let's see
what the tomorrow's integration will report.
Dmitry
19.06.2013 17:45, Adriano dos Santos Fernandes wrote:
As a related topic, there were TCS tests already failing after previous
SEQUENCE command changes.
I started to debug it but didn't finished.
The problem was about SET GENERATOR (which was a DML command) and
transaction visibility.
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 2.5.2 Update 1, 2.1.5 Update 1, 2.5.2, 2.1.5, 2.0.7,
2.5.1, 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.1.0
Reporter: Dmitry Yemanov
The local buffer of MAX_KEY
901 - 1000 of 1223 matches
Mail list logo
