On 04/26/2014 08:16 PM, Leyne, Sean wrote:
I regularly find myself having to merge two (or more) records referenced by
numerous foreign keys... resulting in having to update many tables to
perform this merge. I would find it really useful if there was (and maybe
there already is and I just
New built-in functions for working with unix time
-
Key: CORE-4406
URL: http://tracker.firebirdsql.org/browse/CORE-4406
Project: Firebird Core
Issue Type: New Feature
Components: UDF
27.04.2014 23:04, Jesus Garcia wrote:
I know there is replications applications in firebird, but them are not what
is needed.
What features you are missing in them?
--
WBR, SD.
--
Accelerate Dev Cycles with
28.04.2014 01:04, Jesus Garcia wrote:
Allways my customers require me features that oracle and sql server has
Well, they should understand that Firebird will never have all those
features from Oracle and MSSQL. The question is what they really need.
1. Built-in replication. Our customers
Grant and Revoke update (field)
---
Key: CORE-4407
URL: http://tracker.firebirdsql.org/browse/CORE-4407
Project: Firebird Core
Issue Type: Bug
Components: Security
Affects Versions: 2.5.2
My list is as follows.
optimizer
1. Enable use MERGE / HASH JOIN for OUTER JOINs
2. Performing EXISTS / IN SEMI JOIN as including using MERGE / HASH, and
NESTED LOOP using index
3. HASH aggregation Add to an existing method using sorting
4. Conditional INDEX ONLY SCAN as in Postgresql (dimitr
On 04/28/14 12:44, Dmitry Yemanov wrote:
3. Service calls for aliases.conf CORE-1422
It's named databases.conf in v3 and its structure is quite different
now. IMO, this ticket needs adjustments to the new realities before
considering it for implementaion.
This request requires relatively
28.04.2014 14:14, Simonov Denis wrote:
3. Built as a plug -row replication . The standard delivery enable
replication between servers firebird. For other servers, you can write
your own plugin.
I'm sleeping on it.
Create a bunch of triggers to support replication is not the nicest way.
Sean wrote :
There are existing ways to resolve this:
Of course ... I was just proposing a feature which would be IMO useful for many
users, I never said there were no simple way around as SPs using System tables
(but having to be implemented by every firebird user)...
1- Rethink your
(Context: this is a reply to a thread from November 2013 about porting
Firebird to 64-bit ARM)
-=| Alex Peshkoff, 29.11.2013 15:34:02 +0400 |=-
I will apply a patch commented in opder to avoid conflicts with
class IDs.
Alex, thanks for adding this to the B2_5_Release branch. It seems it
On 24/04/14 11:19, Dmitry Yemanov wrote:
This message is the invitation to both project members and users who
closely follow the development.
UTC time zone support. Vital for international work and handy even for
general use.
It doesn't look like v3 has it (are we sure v3 can't catch this
28.04.2014 16:14, Simonov Denis wrote:
My list is as follows.
Thanks, but I seemed to explicitly state that plain wishlists don't
count. Choose top five from your list, start separate thread per feature
and argue why we should prefer these features over other ones.
Dmitry
Here is my list:
1) I still would like to see this implemented (without the need of external
mechanisms), but I'm not sure if it would be possible at all:
http://tracker.firebirdsql.org/browse/CORE-1738
2) I second Jesus Garcia request for native replication, since people at
FDD and in
On 28-4-2014 16:29, Carlos H. Cantu wrote:
8) Enhancement to the numerics calculations. The currently rule of
summing the scale of the types involved in muls/divs is very bad and
can easily cause overflow. Maybe FB could automatically truncate the
result to the maximum precision possible to
Merge records referenced by FK
--
Key: CORE-4408
URL: http://tracker.firebirdsql.org/browse/CORE-4408
Project: Firebird Core
Issue Type: New Feature
Reporter: Evelyne Girard
Priority:
I created an ticket in the tracker so others who would find this feature useful
can vote for it and discuss this...
http://tracker.firebirdsql.org/browse/CORE-4408
Thank you.
-Message d'origine-
De : Alex
Sean, certainly it's possible to replace almost any of higher than
plain
On 28/04/2014 12:57, Evelyne Girard wrote:
I created an ticket in the tracker so others who would find this feature
useful can vote for it and discuss this...
http://tracker.firebirdsql.org/browse/CORE-4408
If I understood this, why you didn't use cascade foreign keys on the
base tables and
DY Thanks, but I seemed to explicitly state that plain wishlists don't
DY count.
It seems that I also didn't understand that you wanted separated
messages for each feature discussion :(
[]s
Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br
Hi,
If i can say my proposition. Then my favourite is transaction id as int64. Many
times i must spend weeks to to overcome this limit in projects. Ok, then this
projects are better and faster but cost is also bigger and bigger...
When i think about web develooment i also have problem with
28.04.2014 20:30, Carlos H. Cantu wrote:
It seems that I also didn't understand that you wanted separated
messages for each feature discussion :(
Well, we may start with the features intermixed inside this thread and
then separate them for a more detailed discussion, if necessary.
I just ask
There are two situations where I do not find this convenient :
1) I have to copy Master table records to the destination database so I can
compare values in all fields to decide if they must be merged at first (if I
want to do this using SQL).
2) For many tables, I wish to let the user decide
28.04.2014 19:48, Dalton Calford wrote:
Android and iOS native clients if not native servers, are extremely
important given the market growth in those areas and the lack of a good
solid database engine to work with.
Isn't sqlite solid enough? ;-) At least for the tasks a tablet can run.
A
28.04.2014 18:29, Carlos H. Cantu wrote:
Here is my list:
Arrrgh! :-)
I've skipped the items I have nothing to say about (mostly due to lack
of interest, sorry for fairness).
2) I second Jesus Garcia request for native replication, since people at
FDD and in FireBase's list are always
28.04.2014 18:37, Scott Morgan wrote:
This message is the invitation to both project members and users who
closely follow the development.
UTC time zone support. Vital for international work and handy even for
general use.
Nice reminder, although I don't think it's trivial to implement.
28.04.2014 16:14, Simonov Denis wrote:
optimizer
1. Enable use MERGE / HASH JOIN for OUTER JOINs
2. Performing EXISTS / IN SEMI JOIN as including using MERGE / HASH, and
NESTED LOOP using index
3. HASH aggregation Add to an existing method using sorting
I don't think the optimizer
On 28/04/2014 15:30, Dmitry Yemanov wrote:
2. Add JAVA, .NET PROCEDURE and FUNCTION (not just C++)
You can do it in v3 as soon as someone writes the required interfacing
plugins (external engines). Volunteers anyone?
Java was done, but due to everything (Jaybird and Firebird APIs) being
Enhancement in precision of calculations with NUMERIC/DECIMAL
-
Key: CORE-4409
URL: http://tracker.firebirdsql.org/browse/CORE-4409
Project: Firebird Core
Issue Type: Improvement
2) I second Jesus Garcia request for native replication, since people at
FDD and in FireBase's list are always claiming about the lack of such
feature.
DY Replication is a too common word. What do they really need? Warm
DY standby? Hot standby? Sync replication? Async replication?
This is another one that I missed in my first list:
Alter domain depedence problem when changing VAR(CHAR) size
http://tracker.firebirdsql.org/browse/CORE-1427
Existing comments speaks for itself.
[]s
Carlos H. Cantu
www.FireBase.com.br - www.firebirdnews.org
www.warmboot.com.br -
Hi Dmitry,
On 28 April 2014 13:59, Dmitry Yemanov firebi...@yandex.ru wrote:
Isn't sqlite solid enough? ;-) At least for the tasks a tablet can run.
Today's tablets blow away the server systems I used to run interbase on.
In some cases, they are more powerful than some realtime firebird
-Original Message-
From: Carlos H. Cantu [mailto:lis...@warmboot.com.br]
Sent: Lunes, 28 de Abril de 2014 12:30
DY Thanks, but I seemed to explicitly state that plain
wishlists don't
DY count.
It seems that I also didn't understand that you wanted separated
messages for each
-Original Message-
From: Dmitry Yemanov [mailto:firebi...@yandex.ru]
Sent: Lunes, 28 de Abril de 2014 14:21
7) It is known that mixing DDL/DML in the same transaction can cause
corruption in DBs. If this cannot be 100% fixed, I suggest to
introduce some mechanism to detect such
-Original Message-
From: Dalton Calford [mailto:dalton.calf...@gmail.com]
Sent: Lunes, 28 de Abril de 2014 11:49
For example, you could put each schema into a remote
server/database, allowing for basic clustering (before you
jump on me, I know it is more complex than that, I have
28.04.2014 23:21, Claudio Valderrama C. wrote:
I know people will feel outraged with my opinion, but anyway: make DDL
operations atomic and immediate. Uncommitted DDL and DML working in unison
with stable DB structure is a naive dream, period.
I may be wrong as often, but AFAIU this dream may
We are right now discussing this in our (new) company again. We
implemented replication mechanisms similar to ibreplicator (and probably
others) on our own, as probably did many people. Yes, having this kind
of feature build in would be a big help. Current application design
leads to more and more
-Original Message-
From: Dimitry Sibiryakov [mailto:s...@ibphoenix.com]
Sent: Lunes, 28 de Abril de 2014 18:03
28.04.2014 23:21, Claudio Valderrama C. wrote:
I know people will feel outraged with my opinion, but
anyway: make DDL
operations atomic and immediate. Uncommitted DDL
Em 28/4/2014 18:21, Claudio Valderrama C. escreveu:
-Original Message-
From: Carlos H. Cantu [mailto:lis...@warmboot.com.br]
Sent: Lunes, 28 de Abril de 2014 12:30
DY Thanks, but I seemed to explicitly state that plain
wishlists don't
DY count.
It seems that I also didn't
On 28-04-2014 19:02, Dimitry Sibiryakov wrote:
28.04.2014 23:21, Claudio Valderrama C. wrote:
I know people will feel outraged with my opinion, but anyway: make DDL
operations atomic and immediate. Uncommitted DDL and DML working in unison
with stable DB structure is a naive dream, period.
38 matches
Mail list logo
