Hello,
I'm working on a new release of my application, in which some bigger changes
are supposed to happen. I need some assistance please :)
Sorry, it's a bit long, but it's about a sensitive matter, so I wanted to
provide as many details as possible.
1. The current version
Hi,
3.3 Doing everything manually
Means probably the most work, but appears to be the safest way at the
moment.
3.3.1 I could start with the final UTF8 database, i.e. with all the
structure changes etc. included
3.3.2 The source database would be accessed by a connection with ISO8859_1
Hello,
On our database (FB 2.5) of 150 GB we have 21 bad sectors of 512 bytes (all in
the same block). because of that the backup/restore not work (even with the
-ignore option). And gfix not help us too much because it's freeze and crash
the fb_inet_server (but it's was also the case before
Hello,
we are working on a new release of our application, which will support unicode.
When we started with that, my colleague did some research and ported the
script for the currently used ISO8859_1 database to UTF8.
We then created the UTF8 database and were developing using it all the time.
Hello Stephane,
I assume that your database has good non-corrupted metadata, so you just
need to buy FBDataGuard and export all available records from tables
with problems (using re-export of metadata), then merge good data from
corrupted database and exported records into new healthy
Hello,
I'm doing some research about Firebird 2.5.1 as a preparation for a switch from
Firebird 2.1.3
One of the problems I've just discovered is related to the embedded server:
Windows Embedded now contains a SuperClassic instead of a SuperServer engine.
File locks are shared, so a database
Hello,
our server here has Firebird 2.5.0.26074 64bit installed. It manages the access
to several databases, which have different ODS (11.1, 11.2) as they were
created with different FB versions.
I have two questions here:
1. Everything works fine so far, but I'm wondering if I should / or
Hello,
currently my application is using FB 2.1.3, which was available as a 32bit
version only. It works also on 64bit machines without any problems as far as I
know. I'm considering a change to FB 2.5.1, which is available as 32bit and
64bit version.
I assume FB 2.5.1 32bit will work on
Stephane,
Starting with your subject, you can't delete records in bad sectors. You
can drop tables that have data pages in bad sectors because those pages
aren't touched when the table is dropped. When dropping a table, Firebird
reads the RDB$PAGES table to find the pointer pages and index
Hi *,
The Sparky from Firebird Conference in Italy in 2008 is ready for
re-auction. More info in description: http://r.ebay.com/l7uMc5 .
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
[Non-text portions of this message have been removed]
I forgot to mention I'm using firebird 1.5.5
1) The integer was a typo.
2) The stored procedure in your reply, it's looping through every record
correct?
I guess my question wasn't very clear. What I'm trying to do is have
conditional logic in the where clause.
pseudo code:
Select * from
I forgot to mention I'm using firebird 1.5.5
1) The integer was a typo.
2) The stored procedure in your reply, it's looping through every record
correct?
I guess my question wasn't very clear. What I'm trying to do is have
conditional logic in the where clause.
pseudo code:
Select * from
On 1-11-2012 15:25, patrick_marten wrote:
Hello,
currently my application is using FB 2.1.3, which was available as a 32bit
version only. It works also on 64bit machines without any problems as far as
I know. I'm considering a change to FB 2.5.1, which is available as 32bit and
64bit
Dear John,
If you need help getting ubuntu loaded drop me an e-mail message so I
can be ready and then call me tomorrow.
Sincerely,
Ted
Mark Rotteveel wrote:
On 1-11-2012 15:25, patrick_marten wrote:
Hello,
currently my application is using FB 2.1.3, which was available as a 32bit
14 matches
Mail list logo
