for attachments
created by clients that do support Srp256.
Option 1 (using Srp256 or Srp) is more secure and should be preferred.
Option 2 should only be followed if your application for some reason is
stuck on a connection library that does not support Srp256 or Srp.
Mark
--
Mark Rotteveel
Type: Improvement
Components: Engine
Affects Versions: 3.0.7, 4.0 Beta 2
Reporter: Mark Rotteveel
SQL:2016 defines a clause for LEAD, LAG, FIRST_VALUE,
LAST_VALUE and NTH_VALUE, which specifies if nulls are ignored
(skipped/eliminated) or not. Currently Firebird only
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 18-12-2020 15:58, Norbert Saint Georges wrote:
Mark Rotteveel a écrit :
On 18-12-2020 15:14, Norbert Saint Georges wrote:
Server version LI-V6.3.0.2265 Firebird 4.0 Release Candidate 1 on
centos 8.
What tool are you using that it still uses the old 'InterBase
backwards compatible
Firebird 4.0 etc)?
However, it seems like there is something wrong with that version tag,
because I think it should report 6.4.x.x instead, not 6.3.x.x (which
would indicate Firebird 3).
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists
On 08-12-2020 17:17, Dimitry Sibiryakov wrote:
08.12.2020 17:13, Mark Rotteveel wrote:
So, treating it as an error would be wrong, and potentially confusing.
But the routine is called "setErrors" so it is also confusing when it
is actually called to clean errors.
it is communicated as an error, it is not an error as such, but
instead defines success (or at least 'no errors').
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
is not an error, and shouldn't be treated as
such. The combination isc_arg_gds, 0, isc_arg_end is for example sent by
the server in a generic response when a command completed successfully.
So, treating it as an error would be wrong, and potentially confusing.
Mark
--
Mark Rotteveel
Firebird-Devel
. The problem
here isn't with the client proof hash itself, but with a component that
goes into the client proof hash.
Of course, maybe we could always consider adding a SrpV2, or something
that also internally uses SHA-256 (or better).
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web
On 04-12-2020 17:03, Dimitry Sibiryakov wrote:
04.12.2020 16:20, Mark Rotteveel wrote:
After closer inspection, I found the issue. The SHA-1 hash of DAVIDS
is 00AD377F8297F04FD83DFDBF48AABF316850862F. Seeing that leading zero,
I guessed that might be part of the problem. After stripping
On 04-12-2020 15:55, Adriano dos Santos Fernandes wrote:
On 04/12/2020 11:48, Mark Rotteveel wrote:
This behaviour is a security issue, it leaks existence or
non-existence of the user.
Is it a security issue in any website that if I try to create an account
and it says the user already
On 04-12-2020 14:38, Mark Rotteveel wrote:
A bug was reported today against Jaybird
(http://tracker.firebirdsql.org/browse/JDBC-635), that certain Srp users
cannot authenticate against Firebird 3 when using Jaybird. The issue is
not reproducible with fbclient.
This obviously means
On 04-12-2020 15:10, Dimitry Sibiryakov wrote:
04.12.2020 14:38, Mark Rotteveel wrote:
This obviously means that there is something wrong in Jaybird's SRP
implementation, but so far I have no clue as to what.
SRP allows definitely distinguish cases of unknown user and wrong
password. You
On 04-12-2020 14:58, Alex Peshkoff via Firebird-devel wrote:
On 12/4/20 4:38 PM, Mark Rotteveel wrote:
A bug was reported today against Jaybird
(http://tracker.firebirdsql.org/browse/JDBC-635), that certain Srp
users cannot authenticate against Firebird 3 when using Jaybird. The
issue
will be uppercased if it is not
quoted, and otherwise used as is (without the quotes), see
ClntAuthBlock::loadClnt in interface.cpp.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
implementation, but so far I have no clue as to what.
The reported problem occurs with the user name DAVIDS (and one other
username that wasn't provided). I can report the problem locally with
this username.
Any ideas, or tips how to debug this?
Mark
--
Mark Rotteveel
Firebird-Devel mailing list
On 27-11-2020 09:19, Alex Peshkoff via Firebird-devel wrote:
On 11/26/20 10:46 PM, Mark Rotteveel wrote:
I'm currently writing a driver for the R2DBC specification (a new Java
specification for reactive database drivers). Is it OK if I reserve a
new facility code for R2DBC driver errors
I'm currently writing a driver for the R2DBC specification (a new Java
specification for reactive database drivers). Is it OK if I reserve a
new facility code for R2DBC driver errors (similar like I did in the
past for Jaybird)?
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web
Never mind, I withdraw my question, I had overlooked the fact that this
is a direct equivalent of INSERT INTO (id, colval) values (null, 'abc'),
which doesn't make much sense either.
Mark
On 20-11-2020 10:01, Mark Rotteveel wrote:
Triggered by the question by Walter R. Ojeda Valient
end
end#
set term ;#
commit;
update or insert into uoi_example2(id, colval) values (null, 'abc');
```
In short, was this change intentional, or should this be considered a bug?
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 16-11-2020 17:54, Dimitry Sibiryakov wrote:
16.11.2020 17:46, Alex Peshkoff via Firebird-devel wrote:
Anyway fill free to add pull request with sqlstate support.
On contrary, I would like to forget about it.
Are you talking about sqlcode, or sqlstate?
Mark
--
Mark Rotteveel
with another ICU version) run
gfix -icu your_database
I created: https://github.com/FirebirdSQL/firebird-documentation/pull/13
Could you take a look?
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 05-11-2020 15:29, Alex Peshkoff via Firebird-devel wrote:
On 11/5/20 5:03 PM, Mark Rotteveel wrote:
I just tried to drop the LegacyAuth SYSDBA account from the security
database, but this only results in:
SQL> drop user sysdba using plugin Legacy_UserManager;
Statement failed, SQLST
ick Srp,
ignoring the UserManager setting in firebird.conf.
As a result, requiring a strong password for SYSDBA (by only using Srp
for admin accounts) is impossible if you also need to be able to support
LegacyAuth for other accounts.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list,
ix" in chapter 11
"Monitoring & Command-line Utilities". The same goes for the associated
services changes (should be in "API Improvements" of chapter 4 "Changes
to the Firebird API and ODS").
Can someone (Alex) writ this? Or alternatively, give me sufficient
i
Project: Firebird Core
Issue Type: Improvement
Components: Engine
Affects Versions: 4.0 Beta 2
Reporter: Mark Rotteveel
Currently the syntax of a timezone offset in a timestamp or time literal is a
bit too flexible (allowing [+|-][H]H[:[M]M], so 2, 2:0, 02:00, 2
On 24-10-2020 23:51, Adriano dos Santos Fernandes wrote:
Please create a ticket for this.
Done: http://tracker.firebirdsql.org/browse/CORE-6429
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
TIME
::=
TIMESTAMP
::=
::=
::=
::=
::=
::=
::=
::=
[ ]
::=
::=
::=
::=
::=
::=
::=
[ [ ] ]
::=
::=
::=
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/li
://tracker.firebirdsql.org/browse/JDBC-534
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 20-10-2020 12:40, Roman Simakov wrote:
вт, 20 окт. 2020 г. в 13:28, Mark Rotteveel :
Because documentantion here
(https://firebirdsql.org/en/firebird-date-literals/) says they are valid
separators.
Keep in mind, that link is an excerpt from Helen Borrie's Firebird Book
from 2004 (Firebird
That said, I think allowing spaces between date elements would be fine.
Personally, I think Firebird should add support for a cast with a cast
template, CAST( AS [FORMAT ])
as defined in SQL:2016 6.13 and 9.44 Datetime
templates, which would allow to do away with some ambiguity.
Mark
--
Mark
Firebird-3.0.5.33220-0_x64 on Windows 10
Reporter: Mark Rotteveel
When using a parameter in LAG, LEAD or NTH_VALUE window functions, Firebird
returns the error "Dynamic SQL Error; SQL error code = -804; Data type unknown
[SQLState:HY004, ISC error code:335544573]"
For examp
The short answer is 'probably not'.
The long answer is that, unless someone volunteers to write this, or a
company commissions this, it is unlikely such documentation will surface
any time soon.
For point 2, the only migration you need to do is backup your database
in your current version
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0.5, 4.0 RC 1
Environment: Firebird-4.0.0.2211-0_x64 on Windows 10
Reporter: Mark Rotteveel
The support for the RETURNING clause in MERGE is inconsistent, the types
I just noticed that SEC$DB_CREATORS (in Firebird 3) does not restrict
visibility. Any user can see all users granted the CREATE DATABASE
privilege. I would expect only SYSDBA (or users with RDB$ADMIN active)
to be able to see all users.
Is that intentional, and if so why?
Mark
--
Mark
On 2020-08-31 00:09, Eliezer Riani wrote:
Hi,
I have some systems developed in Delphi, PHP, and Java.
I used Firebird 2.5.9 until I've updated to the Firebird 3.0.6 without
any change in my SQL's.
I am now testing Firebird 4.0 from your daily builds and have a
problem. The feature implemented
On 2020-08-25 15:00, Jiří Činčura wrote:
I suppose the EXTENDED timestamp/time format is only for data from
server to client, correct? The other direction (client --> server)
doesn't make sense to me.
When using EXTENDED, the parameters are described as EXTENDED, and you
although don't need
other UDR: just library and SQL script.
What is your argument against making it built-in? Having it built-in
ensures that you can rely on it being present without having to take
explicit action.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https
rebird-devel
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
i = 0;
while (i < 150)
do
begin
execute procedure rdb$blob_util.append(bh, s);
i = i + 1;
end
insert into t (b) values (rdb$blob_util.make_blob(:bh));
end!
commit!
--
--
Mark Rotteveel
Firebird-Devel mailing list, web interfa
name in variable we can make that form of
HASH() return maximum required integer (up to int128 if we support
something like MurmurHash3) and appropriate form of CRYPT_HASH() return
vabinary of maximum required length.
This sounds like a reasonable compromise.
Mark
--
Mark Rotteveel
Firebird-D
e -13"
Key: CORE-6389
URL: http://tracker.firebirdsql.org/browse/CORE-6389
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0.6, 4.0 Beta 2, 2.5.9
Reporter: Mark Rotteveel
Attempts to assi
On 14-08-2020 14:21, Dimitry Sibiryakov wrote:
14.08.2020 13:56, Mark Rotteveel wrote:
b) Otherwise, there shall be no between the
and the , and the set of characters
contained in the shall be wholly contained
in the character set specified by the .
a) If the specifies a specification
, Firebird would need to implement Unicode
literals, because in unicode literals, the introducer serves as a form
of cast.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
to get CVE 'Firebird suggests unreliable hashes for
crypto purposes'.
That is a strawman, and not a very good one.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
for a separate HASH_TOHEX function.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 10-08-2020 18:28, Alex Peshkoff via Firebird-devel wrote:
On 2020-08-10 18:57, Mark Rotteveel wrote:
In any case that could be tackled because HASH( USING
) is a different function than HASH( USING
) and thus can have different return type (eg
VARBINARY that is long enough for all hashes
add CRC64 ?
Nothing in the name of HASH suggests that all hashes applied must be
cryptographic. Currently HASH also supports PJW (as in HASH(value))
which is non-cryptograhic. We could even make this explicit by adding
HASH(value USING PJW) as an alias for HASH(value).
Mark
--
Mark Rotteveel
Fire
On 10-08-2020 12:23, Alex Peshkoff via Firebird-devel wrote:
On 2020-08-02 13:52, Dmitry Yemanov wrote:
02.08.2020 13:14, Mark Rotteveel wrote:
Firebird 4 introduces the function CRC32 which generates a CRC32
hash, while Firebird 4 also introduces an extension to the HASH
function to add
CORE-6384
URL: http://tracker.firebirdsql.org/browse/CORE-6384
Project: Firebird Core
Issue Type: Bug
Components: ISQL
Affects Versions: 4.0 Beta 2
Environment: 4.0.0.2133-0 on Windows 10 64-bit
Reporter: Mark Rotteveel
As isq
On 05-08-2020 10:53, Mark Rotteveel wrote:
On 05-08-2020 03:34, Adriano dos Santos Fernandes wrote:
I'm looking at different behavior of standalone ALTER SEQUENCE RESTART
and IDENTITY COLUMN RESTART.
If standalone sequence is created with initial value 10, then later
RESTARTed WITH value 20
of precision, on the other hand I
think this will bring a lot of pain.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
ax.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 04-08-2020 16:58, Adriano dos Santos Fernandes wrote:
On 01/08/2020 12:04, Mark Rotteveel wrote:
I'd like to know if there are plans to fix
http://tracker.firebirdsql.org/browse/CORE-6084
I will have (another) look.
It might be good to look at it together with CORE-6376, which
Firebird 4 introduces the function CRC32 which generates a CRC32 hash,
while Firebird 4 also introduces an extension to the HASH function to
add (cryptographic) hashes.
Would it make sense to remove CRC32 as a standalone function and instead
add it to HASH?
Mark
--
Mark Rotteveel
Firebird
URL: http://tracker.firebirdsql.org/browse/CORE-6377
Project: Firebird Core
Issue Type: Bug
Components: GBAK
Affects Versions: 4.0 Beta 2
Environment: Firebird-4.0.0.2126-0_x64 on Windows 10
Reporter: Mark Rotteveel
A database
Core
Issue Type: Bug
Components: Engine
Affects Versions: 4.0 Beta 2
Environment: Firebird-4.0.0.2126-0_x64 on Windows 10
Reporter: Mark Rotteveel
When using an identity column with an explicit START WITH clause, it starts
with the wrong value:
SQL
I'd like to know if there are plans to fix
http://tracker.firebirdsql.org/browse/CORE-6084
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Project: Firebird Core
Issue Type: Bug
Components: Engine, Security
Affects Versions: 4.0 Beta 2
Environment: Firebird-4.0.0.2126-0_x64 on WIndows 10
Reporter: Mark Rotteveel
An unprivileged user (as in: newly created, nothing explicitly
On 2020-07-09 09:10, Pavel Cisar wrote:
MArk,
Dne 08. 07. 20 v 20:51 Mark Rotteveel napsal(a):
Says who? Why 2020-01-01 and not other date? Because Firebird uses it
does not make it right, it just make it consistent with Firebird.
Also
mind that DTS is just one from possible time shifts
rse("2020-06-01T20:58:00"), zone);
System.out.println(dt2);
System.out.println(dt2.toOffsetDateTime());
The following is printed:
2020-01-01T20:58+01:00[CET]
2020-01-01T20:58+01:00
2020-06-01T20:58+02:00[CET]
2020-06-01T20:58+02:00
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interfa
On 08-07-2020 20:16, Pavel Cisar wrote:
Mark,
I use iUtil
Dne 08. 07. 20 v 17:44 Mark Rotteveel napsal(a):
The thing is, TIME WITH TIME ZONE for named time zone should be
considered at 2020-01-01, so the relevant DST rule for that date is
in effect.
Says who? Why 2020-01-01 and not other
On 08-07-2020 16:54, Pavel Cisar wrote:
Dne 08. 07. 20 v 15:32 Mark Rotteveel napsal(a):
The problem is how this is handled in Python standard library. It does
define only abstract base class for timezone handling
(https://docs.python.org/3.8/library/datetime.html#tzinfo-objects).
There are two
nt to CEST on
dates in summer time (CEST is just a dumb alias for CET during summertime).
However, it is highly recommend to stop using those short form zone
identifiers as they are ambiguous. It is better to use the long form
identifiers like Europe/Prague.
Mark
--
Mark Rotteveel
Fire
On 2020-06-18 14:02, Dimitry Sibiryakov wrote:
18.06.2020 13:59, Mark Rotteveel wrote:
So while a master is a specific type of owner, the term owner itself
does not have the same meaning as master.
So we can safety replace "master/slave" with "owner/owned",
On 2020-06-18 11:36, Dimitry Sibiryakov wrote:
18.06.2020 10:05, Mark Rotteveel wrote:
BTW, when you start your search-and-replace work, don't forget to
find substitutions for "owner", "invalid", "dependency" and
"creator".
First and third offend e
On 2020-06-18 00:06, Dimitry Sibiryakov wrote:
18.06.2020 00:00, Leyne, Sean wrote:
"they" is also accepted as a singular, although it seems
ungrammatical.
Ok, thanks.
BTW, when you start your search-and-replace work, don't forget to
find substitutions for "owner", "invalid",
On 2020-06-17 22:07, Dimitry Sibiryakov wrote:
17.06.2020 21:55, Mark Rotteveel wrote:
the commonly accepted gender-neutral term is singular they.
I don't know English well enough, sorry. What is singular for
"they"? "This"..?
Singular they is simply using &quo
terminology for another - accepted - inclusive
terminology won't hurt you.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
correct word "it" instead of offending "he" and
"she" in public support list.
Using 'it' for people is pretty offensive, the commonly accepted
gender-neutral term is singular they.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.
executing a subquery.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 04-06-2020 19:49, Adriano dos Santos Fernandes wrote:
On 04/06/2020 14:41, Mark Rotteveel wrote:
On 03-06-2020 19:29, Adriano dos Santos Fernandes wrote:
Now the main engine path for IN/ANY/ALL is ANY.
ALL is early converted to NOT ANY.
Exactly what logic transformation are you applying
to x <> NOT ANY(..)? and `!<` to `>=`, etc?
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 2020-06-03 12:51, Lester Caine wrote:
On 03/06/2020 09:24, Alex Peshkoff via Firebird-devel wrote:
Has
https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
Been replaced with something more up to date?
On 2020-06-02 23:32, Adriano dos Santos Fernandes wrote:
On 02/06/2020 16:45, Mark Rotteveel wrote:
Documentation should be improved for this case too.
This essentially means that
select * from atable where sometimecolumn > current_time;
will yield different results when the time z
On 02-06-2020 21:34, Adriano dos Santos Fernandes wrote:
On 02/06/2020 16:11, Mark Rotteveel wrote:
Maybe it is better if CURRENT_TIME doesn't use the named zone, but
instead always uses an offset based value.
I'm not sure it is. This would create other inconsistencies
(cast(current_timestamp
T_TIME doesn't use the named zone, but
instead always uses an offset based value.
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
anything helpful and has only
served to confuse people. But I feel like I'm starting to repeat myself.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 01-06-2020 16:07, Alex Peshkoff via Firebird-devel wrote:
On 2020-06-01 16:54, Mark Rotteveel wrote:
On 01-06-2020 11:57, Alex Peshkoff via Firebird-devel wrote:
Legacy approach of pre-initializing with well known to the world
password is very bad idea. Not to tell much words about security
about creating a user, I'm talking about initializing
the security database so the necessary tables for SRP already exist.
That should not necessitate the creation of a user (and if it currently
technically does require that, then that is a deficiency that should be
addressed).
Mark
--
Mark
On 30-05-2020 21:32, Adriano dos Santos Fernandes wrote:
On 29/05/2020 17:07, Mark Rotteveel wrote:
Similar problems apply for `(null = any (..))`, this should produce TRUE
when the subquery is empty, but NULL when non-empty.
`(null = any (..))` should not produce TRUE.
See my reply
but its descriptor is not marked as NULL'able, thus client shows FALSE
instead of NULL.
I reported http://tracker.firebirdsql.org/browse/CORE-6322
The SQLDA_DISPLAY ON shows the columns as nullable.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https
Issue Type: Bug
Components: Engine
Affects Versions: 4.0 Beta 2, 3.0.5
Reporter: Mark Rotteveel
The IN predicate and quantified comparison predicates behave incorrectly with
NULL. According to SQL:2016-2, the result of `null in (non-empty list or
query)`, `null
It is the default for Firebird 4. Personally I don't see why the
security database distributed with Firebird 4 (and Firebird 3 for that
matter) can't be either pre-initialized for SRP, or automatically
initialized on first use.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface
On 29-05-2020 22:07, Mark Rotteveel wrote:
Similar problems apply for `(null = any (..))`, this should produce TRUE
when the subquery is empty, but NULL when non-empty.
I meant to say this for `(null = all (..))`...
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https
On 29-05-2020 21:43, Mark Rotteveel wrote:
I was just testing some claims in the Firebird Language Reference
against Firebird 3 and 4, and ran into the following oddity:
The result of `null in (non-empty list or query)` and `null = any
(non-empty query)` should be `null` (see SQL:2016-2, 8.4
so no result, where as
`not (false)` => true, so would have produced a result.
Any idea what might be happening here?
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 2020-05-29 14:01, Pro Turm wrote:
2) No, I meant executing gsec independently from the install.sh
As gsec was deprecated with Firebird 3 and might be removed from future
Firebird versions, it is probably good to get in the habit of using the
SQL user management statements instead of gsec.
On 2020-05-29 09:27, Pro Turm wrote:
2)
Ubuntu 20.04
Firebird Beta2
Installed firebird with sydba and password ending with "!!" (without
quotation marks).
gsec couldnt start with a password ending with "!!".
Did you manually execute gsec, or is the install script still relying on
gsec? With
On 2020-05-28 00:35, Adriano dos Santos Fernandes wrote:
On 27/05/2020 17:54, Mark Rotteveel wrote:
Not having users at all is just a special case of not having the right
username or password. The error for the end-user should be the same in
both cases.
That the administrator gets the same
SYSDBA user.
So, resolution steps are almost identical, which means they don't
warrant a separate error message in my opinion.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
storical problem. For example, CAST(1 AS TIMESTAMP)
will result in a similar error "conversion error from string "1"", while
it is not a string, but an integer.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 27-05-2020 22:04, Mark Rotteveel wrote:
I don't think creating random user just to create plugin tables is
good idea.
I wasn't suggesting to create a random plugin, [..]
I meant to say "random user"...
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface
er reading the Firebird 3 Quick Start Guide, most of it also
applies to Firebird 4:
https://www.firebirdsql.org/file/documentation/reference_manuals/user_manuals/html/qsg3.html
And, there is no 'best' architecture. Each has their own strong points,
and tradeoffs.
Mark
--
Mark Rotteveel
Fire
On 27-05-2020 18:16, Vlad Khorsun wrote:
27.05.2020 17:11, Mark Rotteveel wrote:
On 2020-05-27 13:35, Vlad Khorsun wrote:
27.05.2020 14:29, Dimitry Sibiryakov wrote:
27.05.2020 13:26, Vlad Khorsun wrote:
In my opinion, the message should be more informative for end user,
show waht to do
On 2020-05-27 13:35, Vlad Khorsun wrote:
27.05.2020 14:29, Dimitry Sibiryakov wrote:
27.05.2020 13:26, Vlad Khorsun wrote:
In my opinion, the message should be more informative for end
user,
show waht to do to fix error and refers to the documentation only in
order to get a full
On 2020-05-26 23:13, Ivan Přenosil wrote:
I am testing new include_data switch in FB4 Beta2. Any idea what am I
doing wrong?
All these commands seem to work, except the last one which raises the
exception:
GBAK -b -user sysdba -password masterkey localhost/:Z:\xx.FDB
Z:\xx.fbk -skip_data
This looks like a bug in the statement parser. It seems to use signed 16
bit int for this value, instead of an unsigned 16 bit int (or a signed
32 bit int). This does make me wonder about the test coverage for this
feature.
Could you create a bug in the tracker?
Mark
On 2020-05-26 08:57,
, it looked like a
conversion issue between smallint and other integer datatypes.
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
ment
uses the syntax "... DELETED BOOLEAN ...".
Since we use FB2.5 that's ok, the engine will create a smallint field,
but in FB4 this will create a BOOLEAN field.
So is not a engine bug ... is a application upgrade bug.
Good to hear you managed to find the problem!
Mark
--
Mark
301 - 400 of 1483 matches
Mail list logo
