Hello, All.
What is the right method to choose subj for a new plugin? Should it be a sum
of version
numbers of all parent classes (ie IVersioned+IPluginModule+IBasePlugin etc)?
--
WBR, SD.
--
HPCC Systems
On 06/10/14 14:19, Dimitry Sibiryakov wrote:
Hello, All.
What is the right method to choose subj for a new plugin? Should it be a
sum of version
numbers of all parent classes (ie IVersioned+IPluginModule+IBasePlugin etc)?
Choosing version is needed only f you add new type of plugin
10.06.2014 13:42, Alex Peshkoff wrote:
Choosing version is needed only f you add new type of plugin - for
existing plugin types version number is already chosen.
And this is exactly what I'm trying to do.
Now let me return to one more aspect. Adding own plugin types by users
was not taken
On 06/10/14 15:51, Dimitry Sibiryakov wrote:
Now let me return to one more aspect. Adding own plugin types by users
was not taken into an account initially. What if we change PluginType
from unsigned to signed and let users' plugin types be negative (like
blob types)? Do you any problems
On 06/09/14 18:28, vv m wrote:
Hi Alex,
I'm attaching the requested file.
flock() system call is detected as non-working on AIX by configure.
Specially strange that I've failed to find something useful in the net
re this.
Alternative (USE_FCNTL) ifdef is definitely less tested.
I will check
On 10/06/2014 08:42, Alex Peshkoff wrote:
What if we change PluginType
from unsigned to signed and let users' plugin types be negative (like
blob types)? Do you any problems here?
Numbers are not a way to name things globally in this world.
As you cited blob sub types, it's an example of
10.06.2014 15:57, Alex Peshkoff wrote:
That's not about versioning, but about choosing a way to assign to
plugins user types not conflicting with system types. Or having plugins
of different types is also completely unnecessary?;)
Actually, yes. I don't understand what you call user types
10.06.2014 19:37, Dimitry Sibiryakov wrote:
Actually, yes. I don't understand what you call user types of plugins and
their
difference from system types, because support for any plugin type must be
coded in
engine code directly. I cannot imagine a way to work with plugin that
provides
On 06/10/14 19:37, Dimitry Sibiryakov wrote:
And once again about versioning: if in future versions you decide to add
one more
method to IVersioned interface, how it'll cope with your autoupgrade system?
Very bad - therefore we will not do it.
I mean that
new unknown methods are
10.06.2014 21:54, Alex Peshkoff wrote:
You are not completely right. Imagine someone adds own provider to
firebird. And that provider except other features wants to load some
modules to perform various user-specific code - that modules can be
treated as firebird plugins, at least plugin
Add precision specification to TIME and TIMESTAMP in datatype and cast
--
Key: CORE-4459
URL: http://tracker.firebirdsql.org/browse/CORE-4459
Project: Firebird Core
Issue
Expressions containing some built-in functions may be badly optimized
-
Key: CORE-4460
URL: http://tracker.firebirdsql.org/browse/CORE-4460
Project: Firebird Core
Issue
Thank you!
Actually, I reproduced it once on Linux also. It happened when
FIREBIRD_LOCK was not set.
P.S. I'm trying to build the same code on HP-UX IA64 and Sun SPARC. Having
core dump on HP on the same stage - create_db on empty.fdb, but the stack
looks different. Should I post details in this
13 matches
Mail list logo
