You can subscribe to this list here.
2001 |
Jan
|
Feb
(1) |
Mar
|
Apr
(36) |
May
(56) |
Jun
(1) |
Jul
(5) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
|
Mar
(15) |
Apr
(5) |
May
(7) |
Jun
(5) |
Jul
(3) |
Aug
(6) |
Sep
(3) |
Oct
(8) |
Nov
(23) |
Dec
(21) |
2003 |
Jan
(25) |
Feb
(37) |
Mar
(59) |
Apr
(11) |
May
(8) |
Jun
(24) |
Jul
(18) |
Aug
(29) |
Sep
(30) |
Oct
(11) |
Nov
(20) |
Dec
(5) |
2004 |
Jan
(43) |
Feb
(24) |
Mar
(61) |
Apr
(14) |
May
(23) |
Jun
(50) |
Jul
(13) |
Aug
(56) |
Sep
(55) |
Oct
(64) |
Nov
(94) |
Dec
(27) |
2005 |
Jan
(40) |
Feb
(10) |
Mar
(55) |
Apr
(20) |
May
(16) |
Jun
(6) |
Jul
(58) |
Aug
(38) |
Sep
(5) |
Oct
(6) |
Nov
(71) |
Dec
(99) |
2006 |
Jan
(6) |
Feb
(15) |
Mar
(22) |
Apr
(9) |
May
(31) |
Jun
(35) |
Jul
(47) |
Aug
(18) |
Sep
(21) |
Oct
(24) |
Nov
(63) |
Dec
(79) |
2007 |
Jan
(22) |
Feb
(40) |
Mar
(47) |
Apr
(69) |
May
(22) |
Jun
(20) |
Jul
(25) |
Aug
(13) |
Sep
(7) |
Oct
(44) |
Nov
(76) |
Dec
(1) |
2008 |
Jan
(26) |
Feb
(30) |
Mar
(120) |
Apr
(14) |
May
(22) |
Jun
(40) |
Jul
(48) |
Aug
(7) |
Sep
(34) |
Oct
(31) |
Nov
|
Dec
(30) |
2009 |
Jan
(9) |
Feb
(6) |
Mar
(9) |
Apr
(2) |
May
(9) |
Jun
|
Jul
(31) |
Aug
(32) |
Sep
(15) |
Oct
(23) |
Nov
|
Dec
(9) |
2010 |
Jan
(19) |
Feb
(9) |
Mar
|
Apr
|
May
(9) |
Jun
(6) |
Jul
(8) |
Aug
(21) |
Sep
(10) |
Oct
(1) |
Nov
(3) |
Dec
(33) |
2011 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
(10) |
May
|
Jun
(9) |
Jul
(23) |
Aug
(2) |
Sep
(35) |
Oct
(36) |
Nov
|
Dec
(4) |
2012 |
Jan
(3) |
Feb
(8) |
Mar
(3) |
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(12) |
Nov
(12) |
Dec
|
2013 |
Jan
(18) |
Feb
(5) |
Mar
(1) |
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
(21) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(11) |
2014 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(6) |
Oct
|
Nov
(29) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
(14) |
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(7) |
Sep
(5) |
Oct
|
Nov
(6) |
Dec
(3) |
2016 |
Jan
(14) |
Feb
(9) |
Mar
(33) |
Apr
(12) |
May
(18) |
Jun
(3) |
Jul
|
Aug
(15) |
Sep
|
Oct
|
Nov
|
Dec
(22) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(10) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(44) |
Nov
(32) |
Dec
(8) |
2018 |
Jan
(2) |
Feb
(25) |
Mar
(16) |
Apr
(11) |
May
(1) |
Jun
(19) |
Jul
(3) |
Aug
|
Sep
|
Oct
(25) |
Nov
|
Dec
|
2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(3) |
2020 |
Jan
(29) |
Feb
(28) |
Mar
(13) |
Apr
(13) |
May
(107) |
Jun
(75) |
Jul
(57) |
Aug
(36) |
Sep
(3) |
Oct
(4) |
Nov
(4) |
Dec
(1) |
2021 |
Jan
(2) |
Feb
(13) |
Mar
(5) |
Apr
(6) |
May
(44) |
Jun
(9) |
Jul
(9) |
Aug
(3) |
Sep
(11) |
Oct
(5) |
Nov
(14) |
Dec
(19) |
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
(1) |
Jun
(1) |
Jul
(13) |
Aug
(6) |
Sep
(2) |
Oct
(7) |
Nov
(2) |
Dec
|
2023 |
Jan
(2) |
Feb
|
Mar
(13) |
Apr
(2) |
May
(31) |
Jun
(12) |
Jul
(5) |
Aug
(5) |
Sep
(27) |
Oct
(7) |
Nov
(25) |
Dec
(7) |
2024 |
Jan
(11) |
Feb
(27) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Paul V. <pa...@vi...> - 2004-01-07 12:49:52
|
Hello Nigel, > I'm interested in writing a few docs for Firebird, as I've been > contributing to FreeBSD forums (under the name of Squidge), and have > found myself enjoying it... Sounds good so far :-) > I don't know XML, DocBook, and can't run OpenOffice, OpenOffice is of no use to us, as it doesn't support DocBook. What you need to know about DocBook in order to write Firebird docs can be learned in less than an hour. I'm currently writing a Firebird Docwriting Howto covering - among other things - how to write DocBook XML. I expect it to be ready in less than a week. > but I can create a PDF in an instant from a documentation engine. I visited your pages, they look really good! And so does the PDF. Can I ask what engine you use to generate it? It does a better job than ours :-) On thing though: the "Firebird Documentation Project" already exists, as a subproject of the official Firebird Project at SourceForce. So if you continue with yours as a separate project, I think you'd better give it another name in order to avoid confusion. > Hopefully, it's a matter of, 'The more, The merrier?' Well, yes and no. The more good documentation, the better. But for the project at SourceForge we a) really want DocBook sources (if you can't produce that, someone else will have to convert it, which takes time), and b) would like to coordinate things a bit so there's not too much overlap. Of course this doesn't mean that WE decide what YOU write about; just that the docwriters talk about what they would like to / are going to write about, so we can make the best possible use of our collective knowledge and skills. If you want to keep your docs outside the SourceForge project, you can basically do as you please, but even then it would be a good idea to keep in touch with the other doccers to avoid duplication. > Are there areas that need urgent focus? I specialise in FreeBSD, > PHP, and Apache-based web-apps, powered by Firebird, so perhaps a > few tutes in that area, or is it saturated already?... Not that I know. *Certainly* not in the SourceForge project. To date, we have very little: an introduction, an MS-SQL-To-Firebird Migration Guide, a Docbuilding Howto, a second Howto in the making and that's it. And I'll start documenting the Firebird API soon. Now there's also a lot of free docs (and pointers to it) available at ibphoenix.com. I suggest you have a look there to see if some of the things you mentioned have already been taken care of, and then decide on what to start with. Greetings, Paul Vinkenoog |
From: Nigel W. <ni...@e-...> - 2004-01-07 06:34:39
|
I'm interested in writing a few docs for Firebird, as I've been contributing to FreeBSD forums (under the name of Squidge), and have found myself enjoying it... I don't know XML, DocBook, and can't run OpenOffice, but I can create a PDF in an instant from a documentation engine. Hopefully, it's a matter of, 'The more, The merrier?' Are there areas that need urgent focus? I specialise in FreeBSD, PHP, and Apache-based web-apps, powered by Firebird, so perhaps a few tutes in that area, or is it saturated already?... Nige. Ps. Pdf to date: http://oc.aims.net.au/fdp/dloads/ DocEngine: as above, but one dir back. |
From: Lou F. <jun...@kr...> - 2004-01-07 00:29:06
|
Hello. I have been using the ODBC driver and would like a help file to explain basics, so I volunteered some time to create one. Then I stumbled into this NG as I should probably make sure what ever I come up with is in a standard format. So, where can I get specific details on where to start. Thanks. |
From: Jose V. <xy...@on...> - 2004-01-03 14:51:34
|
Hello Helen, I sent a email talking about translate documentation to spanish language. I would like to help translating documentation to spanish. Thanks. Helen Borrie escribió: > Hello all, > Are any translators waiting/willing to translate the release notes for > Fb 1.5? We already have French and Russian translations under way. > Spanish, Portuguese, German, Japanese, etc. please contact me or post to > the list, so we can coordinate and perhaps spread the load. > > Sources are in Word 7 (yeah, Erk!) 67 pp. > > heLen > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. > See the people who have HELPED US provide better services: > Click here: http://sourceforge.net/supporters.php > _______________________________________________ > Firebird-docs mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-docs > |
From: Jose V. <xy...@on...> - 2004-01-03 14:22:22
|
Ok Paul, I understand. I have sent a mail to Helen Borrie talk her about my intention to help to transalate manuals to spanish language. I wish you to help in this way. Thanks for your answer. Happy new year! Paul Vinkenoog escribió: > Hello Jose, > > >>Hello guys, I seen that Firebird CD comes with Firebird Reference >>Guide and Firebird User Guide. >> >>My question is where can I download these files ? > > > You can't. These two guides are not free, so you'll have to buy the > CD. If you want free documentation, go to www.ibphoenix.com and follow > the link "Main Downloads". At the downloads page you'll find the > Quickstart Guide right at the top, and the Borland documentation set > way down (click on the link "InterBase Documentation Sets" in the Page > Index, near the top). > > Also read the Release Notes for the Firebird version you are running. > > > Hope this helps, > Paul Vinkenoog > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Firebird-docs mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-docs > |
From: Paul V. <pa...@vi...> - 2004-01-03 12:12:55
|
Hello Jose, > Hello guys, I seen that Firebird CD comes with Firebird Reference > Guide and Firebird User Guide. > > My question is where can I download these files ? You can't. These two guides are not free, so you'll have to buy the CD. If you want free documentation, go to www.ibphoenix.com and follow the link "Main Downloads". At the downloads page you'll find the Quickstart Guide right at the top, and the Borland documentation set way down (click on the link "InterBase Documentation Sets" in the Page Index, near the top). Also read the Release Notes for the Firebird version you are running. Hope this helps, Paul Vinkenoog |
From: Jose V. <xy...@on...> - 2004-01-02 20:20:17
|
Hello guys, I seen that Firebird CD comes with Firebird Reference Guide and Firebird User Guide. My question is where can I download these files ? Thanks in advance. |
From: Paul V. <pa...@vi...> - 2003-12-30 09:26:50
|
> (...) The set in the main document would then come to look like: > > <set> > &firebirdintro; > &migrationmssql; > &docbuildhowto; > &docwritehowto; > ... > ... > <set> Typo: that second <set> should be </set> of course. Grtz, Paul |
From: Paul V. <pa...@vi...> - 2003-12-29 23:38:17
|
Hello all, At present our main document, firebirddocs.xml, looks like this: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "file:../docs/docbookx/docbookx.dtd" [ <!ENTITY preface SYSTEM "file:../docs/firebirddocs/preface.xml"> <!ENTITY firebirdintro SYSTEM "file:../docs/firebirddocs/firebirdintro.xml"> <!ENTITY migrationmssql SYSTEM "file:../docs/firebirddocs/migrationmssql.xml"> ]> <set> <book> <bookinfo> <title>Firebird Database Documentation</title> <copyright> <year>2001-2003</year> <holder>All Contributions are Copyright of their individual contributors.</holder> </copyright> </bookinfo> &preface; &firebirdintro; </book> ...etc. (long lines wrapped) Is there a special reason for this? Wouldn't it be cleaner to move the book tags and bookinfo elements to the book documents themselves? The set in the main document would then come to look like: <set> &firebirdintro; &migrationmssql; &docbuildhowto; &docwritehowto; ... ... <set> Just asking :-) BTW: "book" after !DOCTYPE should be changed in "set", although it doesn't affect the build (afaict). Greetings, Paul Vinkenoog |
From: Paul V. <pa...@vi...> - 2003-12-29 23:18:14
|
Hello all, With my second Howto nearing completion, I'm facing the decision of how to place them in our manual set. Because Howtos are relatively short it seems natural to define them as DocBook <article>s rather than <book>s. Unfortunately, an <article> can not be placed directly in a <set>. (This is a shortcoming of DocBook in my opinion.) So for the time being I've created - in my working copy - a <book> called Firebird Howtos, which in turn contains the Howto <article>s. But this feels awkward - after all, a Howto is an independent document in its own right, just like a book. It just happens to be less bulky... I also think we should be able to render each Howto as a separate PDF, just like the other books (still have to figure out how though: at present all we get is one big PDF containing the entire book set). So now I'm inclined to insert them as <book>s after all when the time comes. Any ideas? Greetings, Paul Vinkenoog |
From: Pavel C. <pc...@us...> - 2003-12-03 08:24:57
|
Hi, On 3 Dec 2003 at 14:50, Rema Remulta wrote: > Just wanna ask the installation instructions of Firebird on RedHat 8 or 9 if available. I worry there is no such document. If you have trouble to install FB there, try latest install script for FB 1.5 RC7 (CS+SS tar.gz package). This script should also reveal all necessary steps to install both, CS and SS (well, with slight differences to FB 1.0.x - def. location and few filenames) Best regards Pavel Cisar (ICQ: 89017288) http://www.ibphoenix.com For all your upto date Firebird and InterBase information |
From: Rema R. <rem...@gr...> - 2003-12-03 06:43:25
|
Hi, Just wanna ask the installation instructions of Firebird on RedHat 8 or = 9 if available. Thanks, Rema |
From: Christian D. <chr...@da...> - 2003-11-26 19:39:20
|
Dmitry, >If a BEGIN..END block doesn't have any matching error handlers and an >exception occurs, then all its actions are undone. Otherwise only the >problematic statement is undone and execution goes to the WHEN block. Rerereread and got it. Please add this important statement to the release notes. Thanks and bye, Christian |
From: Christian D. <chr...@da...> - 2003-11-26 19:09:35
|
Dmitry, >First of all, I'd like to say that IB6 documentation is a bit wrong about >the PSQL exception handling :-) > >> create procedure tst_when_in >> returns (state_txt varchar( 10)) >> as >> begin >> delete from tst >> where id = 1; >> delete from tst >> where id = 2; >> >> begin /* <<< when inside block */ >> insert into tst (id, name) >> values (1, 'Name_1'); >> insert into tst (id, name) >> values (2, 'Name_1'); >> when any do >> state_txt = 'Error!'; >> end /* <<< when inside block */ >> end > >WHEN is always inside a block. The above example has it inside an unnamed >statement-level BEGIN..END one. And how would you unite both inserts to react in a similar way (commit/rollback) on errors - my primary question? Not this way, as I demonstrated! I don't want to discuss FB internals. They work fine. My concern is the syntax in your example, and that's why I posted in firebird-docs. >> create procedure tst_when_out >> returns (state_txt varchar( 10)) >> as >> begin >> delete from tst >> where id = 1; >> delete from tst >> where id = 2; >> >> begin /* <<< when outside block */ >> insert into tst (id, name) >> values (1, 'Name_1'); >> insert into tst (id, name) >> values (2, 'Name_1'); >> end /* <<< when outside block */ >> when any do >> state_txt = 'Error!'; >> end > >WHEN is outside the previously mentioned block, but inside the >procedure-level one. You cannot have a SP/trigger without BEGIN..END >construct. A truism. Again: The procedure level block doesn't concatenate statements for commit/rollback atomicity. See result of tst_when_in. There might not be any row after an error deriving from a statement within the block. Right? >> The resulting table entries: >> tst_when_in : 1 row (id = 1, name = 'Name_1') >> tst_when_out: empty >> >> Both SPs generate a unique constraint error, but in the end the >> content of the table differs. With your favourite (tst_when_in) the >> result from the first insert remains in the table (not desired) while >> only tied together by a begin...end (tst_when_out) both inserts act >> simultaneously and the error initiated by the 2nd insert rolls back >> the first one. > >If a BEGIN..END block doesn't have any matching error handlers and an >exception occurs, then all its actions are undone. Otherwise only the >problematic statement is undone and execution goes to the WHEN block. That >how it works, regardless of how Borland documentation says it. You're right, tst_when_in does have one error handler for both inserts. An abortion of the SP wouldn't occur even on an error during the first insert, but nevertheless the first insert isn't undone after the forbidden 2nd insert! >> So for atomicity the WHEN-clause has to follow the _single_ concerning >> statement resp. begin...end block. >> >> I hope this explains my thoughts sufficiently. > >I just suggest you another vision of the same thing. It may be more >difficult to understand, but that's how the things actually work. WHEN >clause is a part of a BEGIN..END block. Right again, just as everything is part of a greater unit...;-) But regardless of this, as I showed above, the wrapping block definition doesn't unite statements to react similar on errors. To sum it up I think we have to distinguish between error handling and the atomicity of a statement block. For error handling (suppressing SP abortion and executing according commands) a WHEN within the BEGIN...END block is O.K.. But this doesn't apply to commit/rollback-atomicity, which only proceeds in the desired way with the single preceding statement (block), whether this fits the common rules or not. Thanks for your efforts, Christian |
From: Dmitry Y. <di...@us...> - 2003-11-26 14:43:53
|
Christian, First of all, I'd like to say that IB6 documentation is a bit wrong about the PSQL exception handling :-) > create procedure tst_when_in > returns (state_txt varchar( 10)) > as > begin > delete from tst > where id = 1; > delete from tst > where id = 2; > > begin /* <<< when inside block */ > insert into tst (id, name) > values (1, 'Name_1'); > insert into tst (id, name) > values (2, 'Name_1'); > when any do > state_txt = 'Error!'; > end /* <<< when inside block */ > end WHEN is always inside a block. The above example has it inside an unnamed statement-level BEGIN..END one. > create procedure tst_when_out > returns (state_txt varchar( 10)) > as > begin > delete from tst > where id = 1; > delete from tst > where id = 2; > > begin /* <<< when outside block */ > insert into tst (id, name) > values (1, 'Name_1'); > insert into tst (id, name) > values (2, 'Name_1'); > end /* <<< when outside block */ > when any do > state_txt = 'Error!'; > end WHEN is outside the previously mentioned block, but inside the procedure-level one. You cannot have a SP/trigger without BEGIN..END construct. > The resulting table entries: > tst_when_in : 1 row (id = 1, name = 'Name_1') > tst_when_out: empty > > Both SPs generate a unique constraint error, but in the end the > content of the table differs. With your favourite (tst_when_in) the > result from the first insert remains in the table (not desired) while > only tied together by a begin...end (tst_when_out) both inserts act > simultaneously and the error initiated by the 2nd insert rolls back > the first one. If a BEGIN..END block doesn't have any matching error handlers and an exception occurs, then all its actions are undone. Otherwise only the problematic statement is undone and execution goes to the WHEN block. That how it works, regardless of how Borland documentation says it. > So for atomicity the WHEN-clause has to follow the _single_ concerning > statement resp. begin...end block. > > I hope this explains my thoughts sufficiently. I just suggest you another vision of the same thing. It may be more difficult to understand, but that's how the things actually work. WHEN clause is a part of a BEGIN..END block. Dmitry |
From: Christian D. <chr...@da...> - 2003-11-26 14:09:33
|
Dmitry, an example to show what I mean: I create a table TST with PK and uniquwe constraint on NAME create table tst ( id bigint not null, name varchar(20)); alter table tst add constraint tst_fk primary key (id); alter table tst add constraint tst_name_unq unique (name); Then I run the following SPs against this table create procedure tst_when_in returns (state_txt varchar( 10)) as begin delete from tst where id = 1; delete from tst where id = 2; begin /* <<< when inside block */ insert into tst (id, name) values (1, 'Name_1'); insert into tst (id, name) values (2, 'Name_1'); when any do state_txt = 'Error!'; end /* <<< when inside block */ end create procedure tst_when_out returns (state_txt varchar( 10)) as begin delete from tst where id = 1; delete from tst where id = 2; begin /* <<< when outside block */ insert into tst (id, name) values (1, 'Name_1'); insert into tst (id, name) values (2, 'Name_1'); end /* <<< when outside block */ when any do state_txt = 'Error!'; end The resulting table entries: tst_when_in : 1 row (id = 1, name = 'Name_1') tst_when_out: empty Both SPs generate a unique constraint error, but in the end the content of the table differs. With your favourite (tst_when_in) the result from the first insert remains in the table (not desired) while only tied together by a begin...end (tst_when_out) both inserts act simultaneously and the error initiated by the 2nd insert rolls back the first one. So for atomicity the WHEN-clause has to follow the _single_ concerning statement resp. begin...end block. I hope this explains my thoughts sufficiently. Kind regards, Christian |
From: Dmitry Y. <di...@us...> - 2003-11-26 11:49:02
|
Helen, > This is the wrong place to raise it. You need to post this to > firebird-devel, where Dmitry Yemanov will see it. He wrote the new > exception handling code AND prepared the examples... I read this forum too ;-) As for the Christian's question - everything is correct. WHEN clause is part of a BEGIN..END block and it allows to catch exceptions thrown outside that block. No errors in the documentation. Dmitry |
From: Helen B. <he...@tp...> - 2003-11-26 11:32:23
|
Christian, This is the wrong place to raise it. You need to post this to firebird-devel, where Dmitry Yemanov will see it. He wrote the new exception handling code AND prepared the examples... regards, Helen At 06:30 PM 25/11/2003 +0100, Christian Danner wrote: >Hi Helen, > >at the 'SQLCODE and GDSCODE' section of the FB 1.5 Release Notes, I >found the following example: > > BEGIN > ... > WHEN SQLCODE -802 THEN > EXCEPTION E_EXCEPTION_1; > WHEN SQLCODE -803 THEN > EXCEPTION E_EXCEPTION_2; > WHEN ANY DO > EXECUTE PROCEDURE P_ANY_EXCEPTION(SQLCODE); > END > >I would interpret '...' as a list of statements, which the WHENs are >responsible for. > >This syntax matches with a remark in the IB6 Language Reference, page >179: > > IMPORTANT > If used, WHEN must be the last statement in a BEGIN...END block. > It should come after SUSPEND, if present. > > >TTFM? As far as I know a WHEN-Clause (including all-or-nothing >rollback-capability) is relevant only for the _single_ preceding >statement (or BEGIN...END block). Then the upper example would be >misleading and should be replaced by something like: > > BEGIN > ... > END > WHEN SQLCODE -802 THEN > EXCEPTION E_EXCEPTION_1; > WHEN SQLCODE -803 THEN > EXCEPTION E_EXCEPTION_2; > WHEN ANY DO > EXECUTE PROCEDURE P_ANY_EXCEPTION(SQLCODE); > > >Kind regards, > >Christian > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >Does SourceForge.net help you be more productive? Does it >help you create better code? SHARE THE LOVE, and help us help >YOU! Click Here: http://sourceforge.net/donate/ >_______________________________________________ >Firebird-docs mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-docs |
From: Christian D. <chr...@da...> - 2003-11-25 17:31:26
|
Hi Helen, at the 'SQLCODE and GDSCODE' section of the FB 1.5 Release Notes, I found the following example: BEGIN ... WHEN SQLCODE -802 THEN EXCEPTION E_EXCEPTION_1; WHEN SQLCODE -803 THEN EXCEPTION E_EXCEPTION_2; WHEN ANY DO EXECUTE PROCEDURE P_ANY_EXCEPTION(SQLCODE); END I would interpret '...' as a list of statements, which the WHENs are responsible for. This syntax matches with a remark in the IB6 Language Reference, page 179: IMPORTANT If used, WHEN must be the last statement in a BEGIN...END block. It should come after SUSPEND, if present. TTFM? As far as I know a WHEN-Clause (including all-or-nothing rollback-capability) is relevant only for the _single_ preceding statement (or BEGIN...END block). Then the upper example would be misleading and should be replaced by something like: BEGIN ... END WHEN SQLCODE -802 THEN EXCEPTION E_EXCEPTION_1; WHEN SQLCODE -803 THEN EXCEPTION E_EXCEPTION_2; WHEN ANY DO EXECUTE PROCEDURE P_ANY_EXCEPTION(SQLCODE); Kind regards, Christian |
From: Helen B. <he...@tp...> - 2003-11-21 10:21:42
|
Alex, You are in the wrong list. This is the documenters' forum. Try http://www.yahoogroups.com/groups/firebird-support. Subscribe, and post messages to: fir...@ya... Helen (mail admin) At 11:48 PM 20/11/2003 +0100, you wrote: >Hi, > >I'm quite new in firebird world... > >I have attach via odbc a firebird table into ms access... > >everythinks work fine, just when I create a primary key in firebird table >then I can't "insert" data into ms-access linked table. But just modify or >delete that data... is that normal? >How can I insert data into ms-access linked table with primary key >defined... > >Please help. >Thanks, >Alex > > > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >Does SourceForge.net help you be more productive? Does it >help you create better code? SHARE THE LOVE, and help us help >YOU! Click Here: http://sourceforge.net/donate/ >_______________________________________________ >Firebird-docs mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-docs |
From: Giumalex <giu...@ti...> - 2003-11-20 22:46:48
|
Hi, I'm quite new in firebird world... I have attach via odbc a firebird table into ms access... everythinks work fine, just when I create a primary key in firebird table then I can't "insert" data into ms-access linked table. But just modify or delete that data... is that normal? How can I insert data into ms-access linked table with primary key defined... Please help. Thanks, Alex |
From: Helen B. <he...@tp...> - 2003-11-06 10:05:22
|
Petros, This question is off-topic in this list, which is the Firebird documenters' workshop. Also, I see that you already have this thread going for two days in the *correct* forum, which is firebird-support. Helen (lists admin) At 05:21 PM 4/11/2003 +0200, Petros Devis wrote: >Hi all >I'm trying to store rows into a firebird db having Greek characters. >I have declared the types of table's fields as varchar with Character set >WIN1253 and Collation PXW_GREEK. When I'm trying to post data that include >Greek chars, the result is to get an error message saying: >"ISC ERROR MESSAGE >arithmetic exception, numeric overflow, or string truncation. >Cannot transliterate character between character sets" >The firebird Server is Version WI-V6.2.972 1.0.3 and it's installed onto Win >XP professional (English) >Could any one help me please? >Devis Petros >Thessalonica >Greece > > > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >Does SourceForge.net help you be more productive? Does it >help you create better code? SHARE THE LOVE, and help us help >YOU! Click Here: http://sourceforge.net/donate/ >_______________________________________________ >Firebird-docs mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-docs |
From: Petros D. <de...@iq...> - 2003-11-04 15:20:26
|
Hi all I'm trying to store rows into a firebird db having Greek characters. I have declared the types of table's fields as varchar with Character set WIN1253 and Collation PXW_GREEK. When I'm trying to post data that include Greek chars, the result is to get an error message saying: "ISC ERROR MESSAGE arithmetic exception, numeric overflow, or string truncation. Cannot transliterate character between character sets" The firebird Server is Version WI-V6.2.972 1.0.3 and it's installed onto Win XP professional (English) Could any one help me please? Devis Petros Thessalonica Greece |
From: <cd...@no...> - 2003-11-03 15:56:43
|
Hi, I can help with French and Brazilan-portuguese translations ;-) Clément |
From: Paul V. <pa...@vi...> - 2003-11-03 00:34:25
|
Hi all, > About JAVA_HOME: > > - In build.bat JAVA_HOME is used twice, both times in the same line: > first to call Java ("%JAVA_HOME%\bin\java.exe"), and a little later > to add %JAVA_HOME%\lib\tools.jar to the classpath. > > - In build.sh it is only used once, to add $JAVA_HOME/lib/tools.jar to > the classpath. The executable is simply called as "java". > > We seem to assume that the Java 2 executable will be in the search path > on Linux systems, but not on Windows systems. Is there a good reason > for this? To me, it would seem more logical to either call java like > "java" on boths OS'es, or to specify the path on both OS'es. Well, I just did a fresh checkout on a recently installed SuSE 8.2, and when I wanted to build the docs java was not found. It turns out that normal users don't have the java bindir in their path by default. So I think we ought to keep JAVA_HOME in the scripts after all, and change build.sh so that it calls $JAVA_HOME/bin/java instead of just "java". Greetings, Paul Vinkenoog |