On 19/08/2022 10:55, Adriano dos Santos Fernandes wrote:
On 19/08/2022 06:06, Tony Whyman wrote:
On 19/08/2022 00:42, Adriano dos Santos Fernandes wrote:
On 18/08/2022 18:53, Tony Whyman wrote:
IBX for Lazaus follows the original Deplhi IBX approach of adopting PSQL
syntax for named
On 19/08/2022 00:42, Adriano dos Santos Fernandes wrote:
On 18/08/2022 18:53, Tony Whyman wrote:
IBX for Lazaus follows the original Deplhi IBX approach of adopting PSQL
syntax for named parameters.
Can a name be used more than once, and if yes, how is its type deduction?
Adriano
IBX for Lazaus follows the original Deplhi IBX approach of adopting PSQL syntax
for named parameters. For example:Select * From EMPLOYEE where EMP_NO =
:KEYVALUE;It also allows for parameter names that are case sensitive and which
contain special characters by enclosing the parameter name in do
to be precise - after code review I do not see isc_sqlcode() to be maked
as deprecated
but I remember well that it was mentioned somewhere as not recommended
in new development, sqlstate is preferred
The Firebird 4 language reference states:
|"SQLCODE| has been used for many years and should
Aren't you confusing isc_interprete with isc_sql_interprete?
isc_sql_interprete interpets the SQLCode, so it does make sense to drop
it if you are getting rid of SQLCode.
On 17/01/2022 09:54, Alex Peshkoff via Firebird-devel wrote:
On 1/17/22 12:24, Tony Whyman wrote:
In the l
are deprecated for future use? If not, then shouldn't they also be
available via IUtil?
Tony Whyman
MWA
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 08/12/2021 09:13, Dmitry Yemanov wrote:
3) "row count" makes it possible to know the position after
fetchLast() and everything else could be calculated locally by the
client library, thus making the server-supported "current position"
totally unnecessary.
Do I miss anything? Could we agr
le to find an answer by experimenting with the new
behaviour, but that will not stop me moaning that the extension of
Update..Returning has been implemented without keeping faith with
existing code.
On 26/11/2021 16:47, Dimitry Sibiryakov wrote:
Tony Whyman wrote 26.11.2021 17:13:
Legacy code
On 26/11/2021 15:43, Dimitry Sibiryakov wrote:
Tony Whyman wrote 26.11.2021 16:32:
What you appear to be saying is that you have changed/expanded the
semantic of Update...Returning, changed the SQL Statement type
returned and then not expected the change to break any existing code
What you appear to be saying is that you have changed/expanded the
semantic of Update...Returning, changed the SQL Statement type returned
and then not expected the change to break any existing code...
On 26/11/2021 15:01, Dimitry Sibiryakov wrote:
Tony Whyman wrote 26.11.2021 15:28:
3
On 26/11/2021 14:32, Dmitry Yemanov wrote:
26.11.2021 17:28, Tony Whyman wrote:
1. IAttachment.prepare is used to parse 'Update Employee Set
Hire_Date = ? Where EMP_NO = ? Returning LAST_NAME'
2. IStatement.getType is then used to determine the statement type.
OK so far.
3
On 26/11/2021 14:16, Dimitry Sibiryakov wrote:
Tony Whyman wrote 26.11.2021 15:10:
This caused an error message to be generated because only a singleton
row was expected and not a cursor.
Well, all I can say is that "existing connectivity drivers do not
support this feature automagi
should support this feature
automagically.
Well, all I can say is that "existing connectivity drivers do not
support this feature automagically". Is it really then intended
behaviour for Update...Returning to now return an SQL Type of
isc_info_sql_stmt_select?
Tony Whyman
this due to your patch or have there been other changes that
have needed this?
Regards
Tony Whyman
On 26/11/2021 09:10, Dmitry Yemanov wrote:
Mark et al,
Yes, I think that is perfectly acceptable for an initial version.
Scrollable cursors are a bit of an oddity anyway, but having
scrol
Thanks guys for responding. The only issue I have is that the release
notes don't seem to tell you that DSQL scrollable cursors are only
available for local databases.
On 23/10/2021 14:14, Dimitry Sibiryakov wrote:
Mark Rotteveel wrote 23.10.2021 14:31:
I'm not sure why not.
Because of re
ing inet://localhost/employee, then I get a "Feature not supported"
error message with calling FetchPrior (FetchNExt still works).
I see the same behaviour with Firebird 3.0.5 and 4.0.0.
Tony Whyman
MWA
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 23/08/2021 13:03, Alex Peshkoff via Firebird-devel wrote:
The minor bug is that if TAG_BUFFER_BYTES_SIZE is set to > 256MB no
error status is reported on a call to createBatch. Instead, you only
know you have a problem when an error is returned from IBatch::add -
looks like the buffer size i
on a call to createBatch. Instead, you only
know you have a problem when an error is returned from IBatch::add -
looks like the buffer size is simply limited to 256MB.
On 21/08/2021 12:35, Tony Whyman wrote:
On 20/08/2021 16:18, Alex Peshkoff via Firebird-devel wrote:
On 8/20/21 4:01 PM, Tony Whyman
On 20/08/2021 16:18, Alex Peshkoff via Firebird-devel wrote:
On 8/20/21 4:01 PM, Tony Whyman wrote:
You can specify such limit - use IBatch::TAG_BUFFER_BYTES_SIZE
parameter in batch parameters block when creating a batch, default is
16Mb, hard limit - 256Mb. Ywo such buffers will be
Other
suggestions are welcome.
I believe that a solution is necessary because you cannot use IBatch for
any large scale use without knowing what you need to do to recover from
a buffer overflow error without losing user data.
Tony Whyman
MWA
Firebird-Devel mailing list, web interface at
batch.
The problem I have is that this is a silent failure. I am checking the
status vector returned by each IBatch->add, and no problem appears to be
reported.
Should I report this as a bug?
On 16/07/2021 13:50, Alex Peshkoff via Firebird-devel wrote:
On 7/16/21 12:39 PM, Tony Whyman wrot
inline blob exists. What am I missing?
Tony Whyman
MWA
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Hi!
We previously decided that we does not need to maintain API
compatibility within mistakes done in alpha/beta versions.
So interfaces does not need to be versioned between unstable releases.
Well, you may not need to maintain API compatibility, but there does
need to be a clear and systemati
There is an important point sitting here for support of legacy
applications. While a standalone x86 Firebird Server is likely to be of
increasingly little interest, an x86 client library may need to be
supported for much longer. This then gives rise to the question: what
about the embedded serv
On 04/12/2020 16: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
the le
On 04/12/2020 14: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 exis
Is this a character case problem? A quick look at the Firebird SRP code
suggests that the username/password hash is generated using the actual
character string without any transformation to all upper case.
On 04/12/2020 13:38, Mark Rotteveel wrote:
A bug was reported today against Jaybird
(htt
face of these issues. You will
probably end up concentrating on opening an example database using a
basic DPB and reading/writing a limited set of data types.
Regards
Tony Whyman
MWA
On 17/08/2020 16:25, Paul Reeves wrote:
I thought I would port the OO API examples to Object Pascal. After all,
On 08/07/2020 14:00, Pavel Cisar wrote:
TIME WITH TIMEZONE is pointless. It sort off works for "naive" TZ that
does not have things like summer time and other time shifts based on
date. The pytz library does not even allow you to create time with
such tz. The dateutil does, but the usability is
On 15/06/2020 15:37, Alex Peshkoff via Firebird-devel wrote:
On 2020-06-11 18:30, Tony Whyman wrote:
On 11/06/2020 11:18, Pavel Cisar wrote:
This is not a problem for languages like Python, Java and .NET that
don't use these files at all, but C++ & Pascal are still important
languag
t there should be a clear scheme for version
numbering as consistent version numbers are really important when it
comes to backwards compatibility.
Tony Whyman
MWA Software
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
eta 2"
Reporter: Tony Whyman
For testing, I have first set up a simple script i.e.
Create Database 'localhost:/tmp/test.fdb' USER 'SYSDBA' PASSWORD 'masterkey';
SET BIND OF TIME ZONE TO EXTENDED;
Create Table FB4TestData_TZ (
RowID Integer not null,
Time
Type: Improvement
Components: Engine
Affects Versions: 4.0 Beta 2
Environment: All
Reporter: Tony Whyman
A TIME WITH TIME ZONE data type records the time in GMT regardless of whether
or not GMT or a local time is used to input the time value.
In order to
On 29/05/2020 14:33, Alex Peshkoff via Firebird-devel wrote:
On 29.05.2020 16:22, Tony Whyman wrote:
Just tried to check out Beta 2 on Linux Mint 19.3 (= ubuntu bionic
18.04) and found that the binaries have been compiled to use
libncurses6. Ubuntu 18.04 uses libncurses5. You need ubuntu 19.10
Just tried to check out Beta 2 on Linux Mint 19.3 (= ubuntu bionic
18.04) and found that the binaries have been compiled to use
libncurses6. Ubuntu 18.04 uses libncurses5. You need ubuntu 19.10 if you
don't want to go through the bother of backporting libncurses6.
By contrast the most recent d
I have also been having problems with the use of the TIME WITH TIME ZONE
type and have been holding back on posting on the issue until I came up
with a suitable proposal. I wrote down my thoughts on the issue a few
weeks ago and have appended them to the end of this EMail - at the time
of writi
: Engine
Affects Versions: 4.0 Beta 2
Environment: Linux Mint 19.3 amd64 with LI-T4.0.0.1960 Firebird 4.0
Beta 2
Reporter: Tony Whyman
I have set up a test of TIME/TIMESTAMP WITH TIME ZONE arrays. The test is
failing when putslice is called, with the error message reporting an
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 4.0 Beta 1
Environment: Using the FB4 Development Snapshot under Linux Mint 19.3
AMD64
Reporter: Tony Whyman
I have created a table as follows in order to test out FB4 array
I have been investigating how the current development snapshot works
with arrays and the new Firebird 4 data types. So far, the I have the
following results:
1. DECFLOAT(16): works fine. Able to declare an array (e.g. Float16
DecFloat(16) [0:16]), write to array elements, save the row and read
Panic over. I had libtomcrypt0 installed and masquerading as
libtomcrypt1. Correct version now installed and FB4 snapshot working.
On 08/05/2020 14:16, Tony Whyman wrote:
On 08/05/2020 14:07, Alex Peshkoff via Firebird-devel wrote:
On 2020-05-08 16:00, Tony Whyman wrote:
/opt/firebird4b2
On 08/05/2020 14:07, Alex Peshkoff via Firebird-devel wrote:
On 2020-05-08 16:00, Tony Whyman wrote:
/opt/firebird4b2/plugins/libChaCha.so: undefined symbol: chacha_setup
On 08/05/2020 13:54, Alex Peshkoff via Firebird-devel wrote:
On 2020-05-08 15:43, Tony Whyman wrote:
Finally got round
/opt/firebird4b2/plugins/libChaCha.so: undefined symbol: chacha_setup
On 08/05/2020 13:54, Alex Peshkoff via Firebird-devel wrote:
On 2020-05-08 15:43, Tony Whyman wrote:
Finally got round to working out why there was a problem.
If I change the Wirecrypt setting in firebird.conf to
off via Firebird-devel wrote:
On 2020-04-30 12:10, Tony Whyman wrote:
All I get when trying to use the current snapshot and opening a
database is the error message "Invalid Clumplet buffer structure:
path length doesn't match with clumplet".
I am using a test program that works w
In the README.time_zone, the SET BIND OF TIME ZONE TO EXTENDED is
described as being intended to "solve a problem of representing correct
time on clients missing ICU library".
All the text I can find, discusses how this is used when reading a
TIMESTAMP WITH TIME ZONE data type from a database,
All I get when trying to use the current snapshot and opening a database
is the error message "Invalid Clumplet buffer structure: path length
doesn't match with clumplet".
I am using a test program that works with all previous versions of Firebird.
If I try to use ISQL with the example employe
On 29/04/2020 13:59, Adriano dos Santos Fernandes wrote:
There probably should thus be a firebird-tzdata package as part of the
set of (deb/rpm) Firebird packages containing the latest tzdata files.
It should then be easy enough for the package maintainer to roll out
updates to the time zone data
On 29/04/2020 13:27, Adriano dos Santos Fernandes wrote:
On 29/04/2020 08:37, Paul Reeves wrote:
On Wed, 29 Apr 2020 11:59:43 +0100
Tony Whyman wrote:
Hopefully, an installer package will eventually be made available to
automate the process. However, the above manual procedure is all that
On 29/04/2020 13:22, Adriano dos Santos Fernandes wrote:
This has nothing to do with ICU.
There is no ICU tz data package in Ubuntu. The data is with the libicu
package inside the libraries.
OK. That seems to be supported by the ICU documentation.
There probably should thus be a firebird-tzda
On 29/04/2020 12:12, Adriano dos Santos Fernandes wrote:
In Linux (Ubuntu as least) and probably MacOS, the ICU time zone
database is not maintained updated in an Ubuntu release. I guess even if
they rebuild and update the library, it still comes with the original tz
database.
So the process of
Many thanks to those who responded yesterday to my question on ICU
library file installation under Windows. I am in the process of updating
the IBX User Manual to include the Firebird 4 extensions and this
question arose when updating the deployment guidelines. Specifically,
giving IBX users gu
So, I guess this has been added since beta 1. I can see it in the latest
Windows snapshot, but not in the latest Linux snapshot.
So the README should make clear that the tzdata directory only applies
to the Windows builds?
Back to my original concern. While the README file gives an outline of
On 28/04/2020 15:11, Adriano dos Santos Fernandes wrote:
On 28/04/2020 11:05, Tony Whyman wrote:
On 28/04/2020 14:59, Adriano dos Santos Fernandes wrote:
https://github.com/FirebirdSQL/firebird/blob/master/doc/sql.extensions/README.time_zone.md#updating-the-time-zone-database
This text
On 28/04/2020 14:59, Adriano dos Santos Fernandes wrote:
https://github.com/FirebirdSQL/firebird/blob/master/doc/sql.extensions/README.time_zone.md#updating-the-time-zone-database
This text applies to building firebird. I am worrying about the end
user's strategy. My point is that there will
On 28/04/2020 14:47, Mark Rotteveel wrote:
On 28-04-2020 15:43, Tony Whyman wrote:
Apologies. I forgot to mention that I was worrying about using the
ICU for the time zone database rather than character sets.
Why does that worry you?
Mark
Because my understanding is that the ICU is the
Apologies. I forgot to mention that I was worrying about using the ICU
for the time zone database rather than character sets.
On 28/04/2020 14:39, Mark Rotteveel wrote:
On 28-04-2020 15:28, Tony Whyman wrote:
On 28/04/2020 14:22, Adriano dos Santos Fernandes wrote:
Databases (indexes
On 28/04/2020 14:22, Adriano dos Santos Fernandes wrote:
I advise not to do that same thing in Windows as done in Linux, using
the OS ICU.
In Linux situation is less complex, it's a server OS. I also think it
was an incorrect thing started without notice by the distro people.
So is the ICU use
On 28/04/2020 14:22, Adriano dos Santos Fernandes wrote:
Databases (indexes) depends on ICU being the same (same sort key
version) or they need to be backed-up and restored (with gbak) to be
fully functional.
That surprises me, as I thought that a TIMESTAMP WITH TIME ZONE was
stored as a GMT tim
I have noticed that the FB4 snapshot builds for Windows include the icu
files icudt52.dll, etc.
They probably should not be installed for Windows 10 Version 1703
(Creators Update) onwards. Does the Windows installer make such a check
and only install the icu files for older versions of Windows
While on the subject of incompleteness in the Firebird 3 API, I never
found any alternative to the following utility functions from the legacy
API.
isc_sqlcode
isc_sql_interprete
isc_interprete
isc_event_counts
isc_event_block
isc_free
This is not a big deal as these are all local functions wi
Well, it comes as news to me that the array type is unsupported in the new API.
IBX supports the array type with the new FB3 api and it all seems to work fine.
The example demos work with both Firebird 2.5 and Firebird 3.0.To do this, I
had to reverse engineer the FB 2.5 code in order to underst
Yes, the "missing types" problem was fixed earlier today.
ISC_TIMESTAMP_TZ_EX
ISC_SHORT
ISC_TIME_TZ_EX
were all missing from Firebird.pas. It should now compile correctly.
On 19/03/2020 15:38, Norbert Saint Georges wrote:
Tony Whyman a écrit :
See http://tracker.firebirdsql.
See http://tracker.firebirdsql.org/browse/CORE-6207
On 19/03/2020 15:27, Norbert Saint Georges wrote:
for information, the differential from yesterday's "firebird.pas"
139c139,140
< ISC_USHORT = word; { 16 bit unsigned }
---
ISC_USHORT = word; { 16 bit unsigned }
ISC_SHORT =
I have been paying attention recently to the VERSION number for the
IUtil API, and I can't see the logic behind the version numbering
scheme. I am looking at the Firebird.pas file.
In Firebird 3, I see "const VERSION = 13;"
In Firebird 4 Beta 1, I see "const VERSION = 21;"
In the most recent
On 10/03/2020 10:34, Dimitry Sibiryakov wrote:
10.03.2020 09:48, Alex Peshkoff via Firebird-devel wrote:
May be for old windows versions - yes, some problems. All the others
upgrade ICU as a part of regular OS upgrade. I.e. if one already has
local ICU extended format is definitely useless ove
On 04/03/2020 17:16, Alex Peshkoff via Firebird-devel wrote:
On 2020-03-04 20:01, Mark Rotteveel wrote:
What is the purpose of introducing yet another datatype called
EXTENDED TIME/TIMESTAMP WITH TIME ZONE?
Help users missing ICU on the client work with time zones.
I am still trying to get
This is all post Beta 1 stuff. When will there be a Beta 2 release
incorporating EXTENDED TIME(STAMP) WITH TIME ZONE?
On 06/03/2020 09:48, Alex Peshkoff via Firebird-devel wrote:
On 2020-03-06 12:43, Mark Rotteveel wrote:
I'll grudgingly implement support in Jaybird by handling it identical
t
My guess is that you are using the wrong calling convention for Linux.
Note: IBX uses "stdcall" when accessing the Firebird API under Windows,
but changes to using "cdecl" under Linux.
On 26/02/2020 13:30, Massimo Fazzolari wrote:
Hi,
I compiled a Firebird UDF library written in object pasca
Components: Engine
Affects Versions: 4.0 Beta 1
Environment: Linux Mint 19.3 64-bit
Firebird binary installed from firebirdsql.org
Reporter: Tony Whyman
In a simple test of the Firebird 4 engine, I dumped the example employee
database (from a Firebird 3 source
Hence why I reported
http://tracker.firebirdsql.org/browse/CORE-5788
and why SRP256 has been available from Firebird 3.0.4 onwards.
On 09/01/2020 17:25, marius adrian popa wrote:
https://arstechnica.com/information-technology/2020/01/pgp-keys-software-security-and-much-more-threatened-by-new-s
: API / Client Library
Affects Versions: 4.0 Beta 1
Environment: Linux Mint 18.3, FPC 3.0.4
Reporter: Tony Whyman
Priority: Blocker
This bug report is intended to record the changes to Firebird.pas needed for it
to successfully compile under FPC 3.0.4. This is
IBX's Firebird Pascal API uses the IProvider interface to get an attachment.
It uses IAttachment to get a transaction (single database) or
IDtc/IDtcStart for a multi-database transaction.
On 05/12/2019 10:31, Jiří Činčura wrote:
3. A transaction (ITransaction) is disposed of with a "release"
uot;.
In all cases, you should null the pointer to the interface after
disposing of it.
The Firebird Pascal API is object oriented and more than one copy of an
object can reference the same underlying Firebird interface, hence it
always uses reference counter interfaces to dispose of objects.
Regar
There's also the isc_dsql_sql_info() API call (see chapter 6 of the API
Guide). This gives statistics on a per SQL statement basis, and allows
you to get the number of inserts, updates, deletes, etc. performed by
the statement. Note that in the Firebird 3 API this is implemented as
the IStateme
I am just wondering if the requested feature is not already present.
A quick test with isc_database_info, with SYSDBA and a normal user
logged in shows:
- SYSDBA connection: only SYSDBA appears to be returned.
- User connection: only user name is returned.
From the security viewpoint, only a
On 25/06/18 11:17, Dimitry Sibiryakov wrote:
25.06.2018 11:29, Tony Whyman wrote:
Even if it were still computationally infeasible to break Srp today,
it is probably that in the next few years it will be totally broken.
You missed my words "non-theoretical".
There is nothing t
On 25/06/18 10:14, Alex Peshkoff via Firebird-devel wrote:
On 25.06.2018 12:02, Dimitry Sibiryakov wrote:
25.06.2018 10:35, Alex Peshkoff via Firebird-devel wrote:
Afraid you are wrong here. It helps an attacker to detect what
plugin is actually used by server (for example - srp or srp256) an
On 25/06/18 10:02, Dimitry Sibiryakov wrote:
25.06.2018 10:35, Alex Peshkoff via Firebird-devel wrote:
Afraid you are wrong here. It helps an attacker to detect what plugin
is actually used by server (for example - srp or srp256) and use that
info to attack particular plugin later.
Does srp
only.
Tony Whyman
MWA
On 21/06/18 15:15, Mark Rotteveel wrote:
On 21-6-2018 15:57, Alex Peshkoff via Firebird-devel wrote:
On 21.06.2018 16:36, Mark Rotteveel wrote:
That is everything continues to use SHA-1, except the generating of
M itself.
As far as I can see - yes.
The only detail
Perhaps worth noting that the version of Firebird.pas distributed with
IBX for Lazarus is patched with many changes. See
https://svn.mwasoftware.co.uk/viewvc/public/ibx/trunk/fbintf/client/3.0/firebird/Firebird.pas?revision=209&view=markup
This is:
1. To comment out all exception handling. Thi
Issue Type: Improvement
Components: Security
Affects Versions: 3.0.3
Environment: All
Reporter: Tony Whyman
User authentication mechanisms such as SRP are already resistant to brute force
attacks where an attacker cycles through many different
Project: Firebird Core
Issue Type: Bug
Components: Security
Affects Versions: 3.0.3
Environment: All
Reporter: Tony Whyman
Attachments: srp_sha256.patch
This proposed patch results from a security review of the Firebird SRP-6a
implementation
Affects Versions: 3.0.3
Environment: All
Reporter: Tony Whyman
Priority: Minor
The "SET TRUSTED ROLE" SQL statement was added in Firebird 3 and is described
in the release notes as:
"The idea of a separate SET TRUSTED ROLE command is that, when t
Affects Versions: 3.0.3
Environment: All
Reporter: Tony Whyman
Audit and Accountability are important for some users where there is a need to
monitor access and/or modification of data. It is understood that the current
Firebird implementation does allow the creation of
: 3.0.3
Environment: Free pascal Compiler
Reporter: Tony Whyman
Priority: Minor
In order to compile and use with FPC, the Firebird.pas file requires the
following directives to be placed at the top of the file:
{$IFDEF FPC}
{$mode delphi}
{$OBJECTCHECKS OFF
For those interested in using Firebird from Pascal/Lazarus, I've copied
the following announcement to this list.
Tony Whyman
MWA Software
Announcement follows:
MWA Software is pleased to announce the release of IBX2 for Lazarus.
This is formally a pre-release. Although the software has
On 22/11/16 16:56, Alex Peshkoff wrote:
> On 11/22/16 16:42, Tony Whyman wrote:
>> I am trying to find a way of determining whether Engine12 is available
>> as a provider when using the FIrebird 3 API.
>>
>> Enumerating the list of Providers in firebird.conf tells
nd repeated calls to
IPluginSet.next get you nowhere but an unending loop.
Any ideas?
Tony Whyman
MWA
--
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Of course what this does seem to imply is that you can't scan the list
of providers in the configuration file (e.g. using the Firebird API) to
reliably determine which providers are available.
On 21/11/16 16:01, Alex Peshkoff wrote:
Missing providers are ignored.
>Would it be better if the
ibuted" firebird.conf and include "Engine12" in
the list of providers. However, libengine12 is not installed. You need
also to install the firebird3.0-server-core to get this installed.
Is this a problem? Would it be better if the firebird.conf file
correctly reflected
I put it at the beginning
On 05/09/16 10:22, Alex Peshkoff wrote:
> On 09/04/2016 06:26 PM, Tony Whyman wrote:
>> {$ifdef fpc} {$mode delphi} {$endif}
> Yes -Mdelphi is required switch.
>
> And where should be that line added? In the most beginni
Martin,
I had the same problem. You have to add
{$ifdef fpc} {$mode delphi} {$endif}
in order to compile with FPC.
Tony Whyman
MWA
On 04/09/16 14:29, Martin Schreiber wrote:
> On Sunday 04 September 2016 10:34:05 Martin Schreiber wrote:
>> Hi,
>> Currently I am implementi
calls.
Is there any documentation or examples on using this interface?
Tony Whyman
MWA
--
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Yes, the number of times I have caught out by that little oddity.
On 16/10/15 14:29, Alex Peshkoff wrote:
> Which must be present in the end of struct or class
The underlying point is that an sql script parser doesn't have to do a
complete analysis but does have to break up the text into blocks o
Except that there is no more reason for a separator after the final PSQL
END statement than there is in 'C' for a semi-colon after a closing brace.
On 16/10/15 14:01, Ivan Přenosil wrote:
> There are actually two separators/terminators - one to be used in scripts
> to separate commands, one to be
eing
available. My recollection is that it was more complicated adding ISQL
set term compatibility (i.e. having to parse a set term statement) than
it was to count begin/end block nesting and ignore semi-colons except in
the outer block. Anyway, the parser worked regardless of whether set
term
Just out of interest, is OCFS2/DRBD any use as a page/lock server?
On 23/03/15 13:01, James Starkey wrote:
> The major new piece is a separate component, the page server. By
> phase 5, it will be necessary to integrate page change and lock
> manager traffic, so perhaps a better name would be p
On 15/08/14 08:48, Dimitry Sibiryakov wrote:
> Integers are ok, pointers are ok, interfaces are in trouble
This should probably be written in stone somewhere.
Even simple external calls such as fb_get_master_interface are difficult
enough. You have carefully define each data type used and ensure
I was using the Alpha 2 source
On 14/08/14 15:23, Adriano dos Santos Fernandes wrote:
> On 14/08/2014 11:04, Tony Whyman wrote:
>> master := IMaster(GetMaster());
>>
>> The program now does complete without an error, but returns "15" as the
>> version. My rea
on on the call to GetMaster - or at least
the internal call that validates the interface - so there really is
something different between the two structures.
On 14/08/14 14:56, Dimitry Sibiryakov wrote:
> 14.08.2014 14:08, Tony Whyman wrote:
>> I'm not quite sure what you think is
, and the parameters are passed in
right-to-left order. The difference is the addition of the //*this*
pointer
<http://en.wikipedia.org/wiki/This_%28computer_programming%29>//, which
is pushed onto the stack last, as if it were the first parameter in the
function prototype./
On 14/08/14 13:08
1 - 100 of 140 matches
Mail list logo
