2012/6/27 Leyne, Sean :
> Moving to another product is one option, though there are several impediments
> including:
>
> - Time to investigate alternatives
> - Time to implement/setup new solution
> - Time to build data conversion to port the existing case data
>
yes
a lot of work
>
> P.S. Remi
> > > Actually, I just opened the "TIMESTAMP Keyword" case with Atlassian
> >
> > IMHO, you did a little mistake in this ticket - you mentioned
> > Firebird. If you simply had written "what kind of idiot must be DB
> > developer to choose reserved word as a field's name", they wouldn't
> > hav
Make fb_lock_print a bit more handy
---
Key: CORE-3879
URL: http://tracker.firebirdsql.org/browse/CORE-3879
Project: Firebird Core
Issue Type: Improvement
Components: LOCK_PRINT
Reporter:
On Wed, Jun 27, 2012 at 7:35 PM, Leyne, Sean wrote:
>
>
> > > Actually, I just opened the "TIMESTAMP Keyword" case with Atlassian
> >
> >IMHO, you did a little mistake in this ticket - you mentioned
> Firebird. If you
> > simply had written "what kind of idiot must be DB developer to choose
>
> Happened again this morning, and I've got a mini-dump this time; who wants it?
Send me the url where i can download it
Regards,
Vlad
--
Live Security Virtual Conference
Exclusive live event will cover all the ways
-- Original Message ---
From: "unordained"
To: firebird-devel@lists.sourceforge.net
Sent: Fri, 15 Jun 2012 10:59:00 -0500
Subject: [Firebird-devel] incomplete crash report
> I'm only setup (sort of) to get stack traces in my test environment,
> not production. All I have to offer
> > Actually, I just opened the "TIMESTAMP Keyword" case with Atlassian
>
>IMHO, you did a little mistake in this ticket - you mentioned Firebird. If
> you
> simply had written "what kind of idiot must be DB developer to choose
> reserved word as a field's name", they wouldn't have had chan
27.06.2012 17:30, Leyne, Sean wrote:
> Actually, I just opened the "TIMESTAMP Keyword" case with Atlassian
IMHO, you did a little mistake in this ticket - you mentioned Firebird. If
you simply
had written "what kind of idiot must be DB developer to choose reserved word as
a field's
name", t
Mark,
> if other vendors do include SQL-2003 reserved words, Jaybird could do so as
> well.
>
> You could also look at manually changing the /WEB-
> INF/classes/entitydefs/entitymodel.xml file to see if you can solve the
> problem that way (see 'Configuring the Entity Engine for JIRA' in the JIR
On Wed, 27 Jun 2012 17:19:34 +0200, Mark Rotteveel
wrote:
> It would be interesting to see what other JDBC drivers report for the
the
> DatabaseMetaData.getSQLKeywords() method. Jaybird explicitly does not
> include TIMESTAMP as that should already be a SQL-92 (and/or SQL:2003)
> reserved word, an
On Wed, 27 Jun 2012 10:47:14 -0400, "Leyne, Sean"
wrote:
>> > -Original Message-
>> > From: Leyne, Sean [mailto:s...@broadviewsoftware.com]
>> > Sent: Viernes, 22 de Junio de 2012 17:18
>> >
>> > > They have a column named TIMESTAMP which is a reserved word
>> > in Firebird,
>> > > and sup
> > -Original Message-
> > From: Leyne, Sean [mailto:s...@broadviewsoftware.com]
> > Sent: Viernes, 22 de Junio de 2012 17:18
> >
> > > They have a column named TIMESTAMP which is a reserved word
> > in Firebird,
> > > and supposedly in many other RDBMS too (and in the SQL
> > standard as
On 27/06/12 11:45, Alex Peshkoff wrote:
> On 06/25/12 16:52, Frank wrote:
>> Any ideas are welcome.
>>
>
> Frank, is this error still reproduced?
No, it is gone, must have been a real rare race condition.
> If yes - can you provide me remote access to that box? (reviewing src
> gave me no idea
Thanks Alex and Dmitry.
Regards,
Thomas
>> gstat output has been changed/extended in Firebird 3. Can somebody
>> comment on the new data returned by gstat? Or perhaps there is some
>> description available in SVN.
>
> Tables:
>
> Primary pointer page: 179, Index root page: 180
>
> Same as b
On 06/25/12 16:52, Frank wrote:
> Any ideas are welcome.
>
Frank, is this error still reproduced?
If yes - can you provide me remote access to that box? (reviewing src
gave me no idea what happens)
--
Live Security Virt
27.06.2012 11:10, Thomas Steinmaurer wrote:
>
> gstat output has been changed/extended in Firebird 3. Can somebody
> comment on the new data returned by gstat? Or perhaps there is some
> description available in SVN.
Tables:
Primary pointer page: 179, Index root page: 180
Same as before.
On 06/27/12 11:10, Thomas Steinmaurer wrote:
> Hello,
>
> gstat output has been changed/extended in Firebird 3. Can somebody
> comment on the new data returned by gstat? Or perhaps there is some
> description available in SVN.
>
fbs2 bin # ./gstat -e employee
Database
"/usr/home/firebird/trunk/g
Hello,
gstat output has been changed/extended in Firebird 3. Can somebody
comment on the new data returned by gstat? Or perhaps there is some
description available in SVN.
Thanks,
Thomas
--
Live Security Virtual Confer
18 matches
Mail list logo
