12.02.2014 23:03, Vlad Khorsun wrote:
Probably. But it is easy to isolate your application from customer's
environment
and make it use your private copy of fbclient.dll + firebird.msg.
Yes. And as the result to get private environment incompatible with the
rest of
system that
Hello,
when I execute a stored procedure which is part of a package with e.g.:
select * from pkg_schema.s_user_tables;
I guess, it would make sense to also have the package name somewhere in
the trace output for the EXECUTE_PROCEDURE_* event. Does this make sense?
Good point. I
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
On 02/13/14 04:52, Hajime Nakagami wrote:
Thanks Marius and others.
I'm trying to implement SRP protocol by pure python.
But something wrong in my python codes, I know.
I have found RemotePassword::getUserHash() return different value with
getUserHash() in srp.py.
On Thursday 13 February 2014 16:39:41 Dimitry Sibiryakov wrote:
13.02.2014 9:19, Vlad Khorsun wrote:
Please, provide real sample of the task you can't solve using
existing facilities and we will think how to improve it.
As I wrote in ticket: fbclient.dll installed into system
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
13.02.2014 0:38, Leyne, Sean wrote:
How so, you create your own install which create a \client folder
underneath your application folder.
You can install:
- your application into the application folder
- firebird.msg into the application folder
- FBCLient.dll into the
13.02.2014 16:51, Dmitry Yemanov wrote:
Do you mean really unreadable or actually readable but prefixed with
cannot locate firebird.msg? Example maybe?
Actually, half-readable. There may be meaningfil lines as well as prefixed
with can't
format message. Example:
unknown ISC error
13.02.2014 16:48, Paul Reeves wrote:
Have you tried setting FIREBIRD_MSG?
Do you mean from my application before calling LoadLibrary()? No. I have no
idea what
value I would have to assign to it.
--
WBR, SD.
13.02.2014 16:56, Leyne, Sean wrote:
There is a distributable for that, which can be incorporated into a install
kit.
This is the way to nowhere. And at the end of this way is staying Exadata:
rented black
box with no access to inside. Unfortunately, the nature of my application does
not
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.
Sounds good.
Thank you,
Thomas
13.02.2014 16:51, Dmitry Yemanov wrote:
Do you mean really unreadable or actually readable but prefixed with
cannot locate firebird.msg? Example maybe?
Actually, half-readable. There may be meaningfil lines as well as prefixed
with can't
format message. Example:
unknown ISC error
13.02.2014 9:19, Vlad Khorsun wrote:
Please, provide real sample of the task you can't solve using existing
facilities and we will
think how to improve it.
As I wrote in ticket: fbclient.dll installed into system directory produces
unreadable
error messages because of absence
13.02.2014 22:02, Vlad Khorsun wrote:
This error code (isc_bad_epb_form) was intorduced in FB 2.5 and it means
you are
used older fbclient.dll with your application when obtained this error from
Firebrid server.
Also it means that firebird.msg corresponding to your old client library
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.
Sounds good.
Check next snapshot build,
13.02.2014 22:11, Vlad Khorsun wrote:
1. Microsoft explicitly prohibited to put anything into system folders (since
Vista, iirc).
Proof, please. Not recommended and explicitly prohibited - two big
differences, you
know.
System folder is the only place where a _shared_ (do you remember
Max Size of VARCHAR / CHAR in Table ad StoredProcedure
--
Key: CORE-4338
URL: http://tracker.firebirdsql.org/browse/CORE-4338
Project: Firebird Core
Issue Type: Bug
Components:
13.02.2014 22:02, Vlad Khorsun wrote:
This error code (isc_bad_epb_form) was intorduced in FB 2.5 and it means
you are
used older fbclient.dll with your application when obtained this error from
Firebrid server.
Also it means that firebird.msg corresponding to your old client library also
ALIAS NAME LENGTH LIMITATION
Key: CORE-4339
URL: http://tracker.firebirdsql.org/browse/CORE-4339
Project: Firebird Core
Issue Type: Bug
Affects Versions: 3.0 Alpha 2
Reporter: Tim Kelly
Just
Restore fails if one stored procedure is incorrect
--
Key: CORE-4340
URL: http://tracker.firebirdsql.org/browse/CORE-4340
Project: Firebird Core
Issue Type: Bug
Components: GBAK
20 matches
Mail list logo
