Hi,
i am really surprised – why reinvent the wheel?
All people use table with version information and this work years.
Table have benefit – you can include version description (what’s new).
At application start or installer – you check if db is up to date or if
instaler is not older than
On 04/12/2015 00:07, Christian Gütter n...@guetter.org
[firebird-support] wrote:
> In Windows this is not an abuse, executable files have
> provision for version metadata ("resource") and you're supposed
> to use it properly. Pity this doesn't apply portably to all file
types, innit.
True,
What you can do is inspect Firebird structure and search for an unused area.
Documentation about this can be found at
http://www.firebirdsql.org/manual/fb-internals.html
By example if you check
http://www.firebirdsql.org/manual/fbint-standard-header.html
Pag_checksum: Two bytes, unsigned. Bytes
That is very dangerous to do, the same bytes might be reused differently in a
newer ODS. Either use a normal Firebird table to store version info, or do it
outside of the database. Do not hack things in the internal structure.
Mark
- Reply message -
Van: "Fabiano Kureck
Fabiano Kureck suggested sticking application version information in the
checksum slot of the page header.
Mark Rotteveel quite correctly responded.
>
>
> That is very dangerous to do, the same bytes might be reused differently
> in a newer ODS. Either use a normal Firebird table to store version
Hi,
> I figured out it is possible to simply append manually some ascii
> data at the end of the db file (see picture attached). This would be
> my preferred solution. It seems to work (I can still read and write
> to the database and even manipulate the database structure). But
> maybe this is
The same could be accomplished by creating a “Application_SchemaVersion” SP
which would return the necessary details.
The advantage would be that no search thru the domain would be required.
Sean
From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Sent: December
On 03/12/2015 14:48, Christian Gütter n...@guetter.org
[firebird-support] wrote:
Or, if you are a big fan of abusing file formats, you might want to
try to append the information to your executable file.
In Windows this is /not /an abuse, executable files have provision for
version metadata
On Windows, all files can have alternative streams with additional data. It is
a form of hidden metadata that is attached to the main filename.
Mark
- Reply message -
Van: "Tim Ward t...@telensa.com [firebird-support]"
Aan:
Mark Rotteveel wrote:
> On Windows, all files can have alternative streams with additional
> data. It is a form of hidden metadata that is attached to the main filename.
True, but the alternate data streams get lost when the file is stored
on a non-NTFS drive, sent via FTP/E-Mail etc. So
Tim Ward wrote:
> In Windows this is not an abuse, executable files have
> provision for version metadata ("resource") and you're supposed
> to use it properly. Pity this doesn't apply portably to all file types,
> innit.
True, but if you just append the info to the exe file, it is an
On Tue, Dec 1, 2015 at 7:42 AM, 'Moessinger, Semjon' s.moessin...@pi.ws
[firebird-support] wrote:
>
>
>
> My main intend is to add some version information to a firebird database
> file, since I will use firebird as embedded database and installers/update
>
Hello,
My main intend is to add some version information to a firebird database file,
since I will use firebird as embedded database and installers/update mechanism
will need this information.
The information should be available platform independent and I would prefer a
solution not needing
14 matches
Mail list logo