Error when compiling the procedure containing the statement if (x = (select
...))
-
Key: CORE-4204
URL: http://tracker.firebirdsql.org/browse/CORE-4204
Project: Firebird
04.09.2013 11:43, Alex Peshkoff wrote:
May be in that case next step? Keep declaring strings as char(N), but
treat N not as maximum size of string
Please don't play against the SQL standard. The declared string length
is a constraint which must be enforced.
Dmitry
On 09/04/13 11:53, Dmitry Yemanov wrote:
04.09.2013 11:43, Alex Peshkoff wrote:
May be in that case next step? Keep declaring strings as char(N), but
treat N not as maximum size of string
Please don't play against the SQL standard. The declared string length
is a constraint which must be
On 09/04/13 11:53, Dmitry Yemanov wrote:
04.09.2013 11:43, Alex Peshkoff wrote:
May be in that case next step? Keep declaring strings as char(N), but
treat N not as maximum size of string
Please don't play against the SQL standard. The declared string length
is a constraint which must be
On 04/09/2013 05:09, Alex Peshkoff wrote:
On 09/04/13 11:53, Dmitry Yemanov wrote:
04.09.2013 11:43, Alex Peshkoff wrote:
May be in that case next step? Keep declaring strings as char(N), but
treat N not as maximum size of string
Please don't play against the SQL standard. The declared string
04.09.2013 12:40, Adriano dos Santos Fernandes wrote:
The name of this type, a long and unlimited string, is CLOB.
But what value will be in XSQLVAR.sqltype?
--
WBR, SD.
--
Learn the latest--Visual Studio 2012,
On 09/04/13 14:46, Dimitry Sibiryakov wrote:
04.09.2013 12:40, Adriano dos Santos Fernandes wrote:
The name of this type, a long and unlimited string, is CLOB.
But what value will be in XSQLVAR.sqltype?
Not sure it will be supported in SQLDA API...
04.09.2013 12:56, Alex Peshkoff wrote:
Not sure it will be supported in SQLDA API...
Why not? There are at least two ways: client-side blob id and
clent-assigned sqldata.
--
WBR, SD.
--
Learn the latest--Visual
On 09/04/13 14:59, Dimitry Sibiryakov wrote:
04.09.2013 12:56, Alex Peshkoff wrote:
Not sure it will be supported in SQLDA API...
Why not?
That all is about the future version of firebird, let's call it FB4.
Certainly (hmm, at least on my mind) we will continue supporting
backward
Unbounded types work very badly with the SQLDA. The original SQLDA was
lifted verbatim from the DB2 spec, circa 1985, because I wanted
something more or less standard. It was pretty much awful then and it
hasn't gotten much prettier since. On the other hand, it's what
everything uses for
Include COST for statement in mon$statements
Key: CORE-4207
URL: http://tracker.firebirdsql.org/browse/CORE-4207
Project: Firebird Core
Issue Type: Improvement
Reporter: Simonov Denis
ISQL -x does not output the START WITH clause of generators/sequences
-
Key: CORE-4205
URL: http://tracker.firebirdsql.org/browse/CORE-4205
Project: Firebird Core
Issue
Add RESTART [WITH] clause for alter identity columns
Key: CORE-4206
URL: http://tracker.firebirdsql.org/browse/CORE-4206
Project: Firebird Core
Issue Type: Improvement
On 04/09/2013 11:00, Jim Starkey wrote:
a blob that is thought to be character
And a string with unlimited length is nothing than a blob that is
thought to be character.
If you implement it efficiently or not, is another matter.
Adriano
A clob is nothing but a blob that is thought to be character.
On 9/4/2013 6:40 AM, Adriano dos Santos Fernandes wrote:
On 04/09/2013 05:09, Alex Peshkoff wrote:
On 09/04/13 11:53, Dmitry Yemanov wrote:
04.09.2013 11:43, Alex Peshkoff wrote:
May be in that case next step? Keep declaring
Dmitry, I tried again with FB3 today's version and it a little bit
different. It stops restoring backup with this:
(...)
gbak:restoring parameter BDSEQCTA for stored procedure
gbak:restoring parameter BDCODCENTROS for stored procedure
gbak:restoring parameter BDCODTPCC for stored
Dmitry, I tried again with FB3 today's version and it a little bit
different. It stops restoring backup with this:
(...)
gbak:restoring parameter BDSEQCTA for stored procedure
gbak:restoring parameter BDCODCENTROS for stored procedure
gbak:restoring parameter BDCODTPCC for stored
O would like to appologies to all...
We have 2 hardcoded UDF's in our database - and we do not use those at all!
So, I removed those UDF's from our database and tried again. It almost
works!
Now I get another problem:
gbak:committing metadata
gbak: ERROR:invalid request BLR at offset 1769
gbak:
04.09.2013 23:34, Fabiano - Desenvolvimento SCI wrote:
Now I get another problem:
gbak:committing metadata
gbak: ERROR:invalid request BLR at offset 1769
gbak: ERROR: BLR syntax error: expected variable identifier at offset
1770, encountered 76
gbak: ERROR: Error while parsing
19 matches
Mail list logo
