Command 'SHOW PROCEDURE' leads ISQL to crash
-
Key: CORE-5274
URL: http://tracker.firebirdsql.org/browse/CORE-5274
Project: Firebird Core
Issue Type: Bug
Components: ISQL
Affects Ver
13.06.2016 0:28, Vlad Khorsun wrote:
>Yes, with test case, pls
CORE-5275. Test case is in standard test suite: bugs.core_1746.
--
WBR, SD.
--
What NetFlow Analyzer can do for you? Monitors network bandwidth an
Test bugs.core_1746 acivates assertion
--
Key: CORE-5275
URL: http://tracker.firebirdsql.org/browse/CORE-5275
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 4.0 I
Hi *,
is there some special format for isc_spb_bkp_skip_data? I'm writing
normal string as usual, but server is not happy "Invalid clumplet buffer
structure: unknown parameter for backup/restore".
I write into SPB { isc_spb_bkp_skip_data, , } so
for say "AA" I send { 8, 2, 0, 65, 65 }.
Running
Looking into CrumpletReader I see:
case isc_action_svc_backup:
case isc_action_svc_restore:
switch (tag)
{
case isc_spb_bkp_file:
case isc_spb_dbname:
Support MULTISET functionality
--
Key: CORE-5276
URL: http://tracker.firebirdsql.org/browse/CORE-5276
Project: Firebird Core
Issue Type: New Feature
Reporter: Vladimir Arkhipov
I think there are many
03.06.2016 16:11, Adriano dos Santos Fernandes пишет:
>
> The major thing to discuss here is, what should be that character limit:
> 64, 128, other?
I'm afraid the new limit should be 63 characters. 64 UTF-8 characters
means 256 bytes which does not fit BLR (string length counter is
single-byte
Dmitry Yemanov wrote:
> 03.06.2016 16:11, Adriano dos Santos Fernandes пишет:
>>
>> The major thing to discuss here is, what should be that
>> character limit: 64, 128, other?
> I'm afraid the new limit should be 63 characters. 64 UTF-8
> characters means 256 bytes which does not fit BLR (string
>
Hi Geoff,
Many times the need for longer metadata names is to compensate for the lack
of other functionality.
For example, due to the extreme functionality of Firebird/Interbase, long
before modern database tools where common, I would preface any object with
an indicator as to what it is, such as
CREATE USER allows to specify with length more than 64
characters,which lead to failure when we further execute SELECT * FROM
SEC$USERS or SHOW USERS
-
On 13/06/2016 09:56, Geoff Worboys wrote:
>
> If this change is going to be lots of work
It's already committed and necessary adjustments should not be complicate.
> then I'd rather see
> the effort put into a more comprehensive solution like the
> option 3 suggested by Dalton Calford.
Nobody
On 06/13/2016 01:12 PM, Jiří Činčura wrote:
> Looking into CrumpletReader I see:
> case isc_action_svc_backup:
> case isc_action_svc_restore:
> switch (tag)
> {
> case isc_spb_bkp_file:
>
Done; CORE-5278.
--
Mgr. Jiří Činčura
Independent IT Specialist
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
CrumpletReader is missing isc_spb_bkp_skip_data and isc_spb_res_skip_data
-
Key: CORE-5278
URL: http://tracker.firebirdsql.org/browse/CORE-5278
Project: Firebird Core
Is
On 06/13/2016 08:20 AM, Jiří Činčura wrote:
>> AFAIR, server ignores (actually, removes) isc_dpb_host_name if it's
>> found in the client-specified DPB. However, isc_dpb_host_name will be
>> preserved for the embedded access (if it makes any sense).
> What about CNCT_login vs isc_dpb_user_name?
>
Non admin user cannot open public view when view references another table, even
if view is given appropriate grants to that table
-
Key: CORE-5279
Grant field rights + grant select to package = internal Firebird consistency
check (bad ACL (293), file: grant.cpp line: 2431)
---
Key: CORE-5280
17 matches
Mail list logo
