[Firebird-devel] [FB-Tracker] Reopened: (CORE-3238) Makes GEN_UUID return a compliant RFC-4122 UUID.

2012-07-10 Thread Adriano dos Santos Fernandes (JIRA)
[ http://tracker.firebirdsql.org/browse/CORE-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano dos Santos Fernandes reopened CORE-3238: > Makes GEN_UUID return a compliant RFC-4122 UUID. > ---

[Firebird-devel] [FB-Tracker] Created: (CORE-3887) CHAR_TO_UUID and UUID_TO_CHAR works different in big/little endian architectures - inverted of CORE-2898

2012-07-10 Thread Adriano dos Santos Fernandes (JIRA)
CHAR_TO_UUID and UUID_TO_CHAR works different in big/little endian architectures - inverted of CORE-2898 Key: CORE-3887 URL: http://tracker.firebirdsql.org/br

Re: [Firebird-devel] Trace API: Improved PSQL tracing?

2012-07-10 Thread Vlad Khorsun
> I think that making everyone pay the cost of the overhead generated by so > many "hooks" inside the engine is a very bad idea. Are you measured trace overhead ? Compare call of a function with cost of statement execution... > For me, it would be a > great thing if all tracing and encrypt

Re: [Firebird-devel] Trace API: Improved PSQL tracing?

2012-07-10 Thread Leyne, Sean
Claudio, > I think that making everyone pay the cost of the overhead generated by so > many "hooks" inside the engine is a very bad idea. This is exactly my point. It seems that the current approach has a high cost for all usage modes. Sean --

Re: [Firebird-devel] Trace API: Improved PSQL tracing?

2012-07-10 Thread Claudio Valderrama C.
> -Original Message- > From: Thomas Steinmaurer [mailto:t...@iblogmanager.com] > Sent: Martes, 10 de Julio de 2012 2:47 > > I and quite a few other Trace API users believe, that a > traced PSQL call > is too much of a black-box currently. We already have a trace > output for > embedde

Re: [Firebird-devel] Trace API: Improved PSQL tracing?

2012-07-10 Thread Thomas Steinmaurer
Hello, >> I am also very skeptical about the "need" that to add this >> functionality to > the Trace API, as it falls into the area of PSQL debugging/profiling > which is not what the current functionality is about*. > > I don't propose to extend the Trace API in a way, whi