🚀 go-pugleaf

In article <3de28d36@newsgroups.borland.com>, eddielee@tropicsoft.com 
says...
> In the system table RDB$FIELDS, for RDB$FIELD_TYPE there are listed types
> such as CSTRING, QUAD, INT64 but when one looks in the "Data Definition
> Guide" these types do not appear and are not discussed. Does anybody know
> why ?
> 
	They're UDF arguments, not column types.

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer

"Craig Stuntz [TeamB]" <cstuntz@nospamplease.com (but use vertexsoftware to
email)> wrote in message
news:MPG.184c59fe634ff0c98a26a@newsgroups.borland.com...
> In article <3de28d36@newsgroups.borland.com>, eddielee@tropicsoft.com
> says...
> > In the system table RDB$FIELDS, for RDB$FIELD_TYPE there are listed
types
> > such as CSTRING, QUAD, INT64 but when one looks in the "Data Definition
> > Guide" these types do not appear and are not discussed. Does anybody
know
> > why ?
> >
> They're UDF arguments, not column types.

Thanks, I haven't looked into UDFs yet. Evidently one can create a UDF out
of data types which are not allowed as built-in types. I am glad you
mentioned UDFs to me since I may want to create a UDF type which uses INT64
instead of the built-in INTEGER type to allow a greater range of values for
a key. Although 4 billion or so is pretty large, I have to anticipate in the
component on which I am working that end-users may want a value larger than
that for their own purposes.

In article <3de2bc72$1@newsgroups.borland.com>, eddielee@tropicsoft.com 
says...
> Thanks, I haven't looked into UDFs yet. Evidently one can create a UDF out
> of data types which are not allowed as built-in types. 
> 
	Sort of.  The UDF types map to IB's regular types.  You use CSTRING 
to pass a CHAR or VARCHAR, for example.

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer

"Craig Stuntz [TeamB]" <cstuntz@nospamplease.com (but use vertexsoftware to
email)> wrote in message
news:MPG.184d6f09a090733298a278@newsgroups.borland.com...
> In article <3de2bc72$1@newsgroups.borland.com>, eddielee@tropicsoft.com
> says...
> > Thanks, I haven't looked into UDFs yet. Evidently one can create a UDF
out
> > of data types which are not allowed as built-in types.
> >
> Sort of.  The UDF types map to IB's regular types.  You use CSTRING
> to pass a CHAR or VARCHAR, for example.

Then why is there an INT64 type mentioned in the system tables as a data
type but not as a data type for columns when creating tables ? A
for-the-future addition which doesn't yet exist in the 6.5 release but made
its way into the 6.0 .pdf documentation set ? BTW, do you know if Borland
intends to update the 6.0 .pdf documentation set distributed with 6.5 to
something more recent or better ?

In article <3de3a6bc$1@newsgroups.borland.com>, eddielee@tropicsoft.com 
says...
> Then why is there an INT64 type mentioned in the system tables as a data
> type but not as a data type for columns when creating tables ? 

	You would use NUMERIC(18,0).  INT64 is probably for UDFs, but I 
haven't looked.

> BTW, do you know if Borland
> intends to update the 6.0 .pdf documentation set distributed with 6.5 to
> something more recent or better ?
> 
	The docs have been updated for IB 7.0.  I would not expect 
documentation updates other than the "Release Notes" for minor releases.

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer

"Craig Stuntz [TeamB]" <cstuntz@nospamplease.com (but use vertexsoftware to
email)> wrote in message
news:MPG.184d77dcdc90bef098a27a@newsgroups.borland.com...
> In article <3de3a6bc$1@newsgroups.borland.com>, eddielee@tropicsoft.com
> says...
> > Then why is there an INT64 type mentioned in the system tables as a data
> > type but not as a data type for columns when creating tables ?
>
> You would use NUMERIC(18,0).  INT64 is probably for UDFs, but I
> haven't looked.
>
> > BTW, do you know if Borland
> > intends to update the 6.0 .pdf documentation set distributed with 6.5 to
> > something more recent or better ?
> >
> The docs have been updated for IB 7.0.  I would not expect
> documentation updates other than the "Release Notes" for minor releases.

I  am working with IB 6.5 which came with a 5 user client-server license
when I upgraded to BCB6. Unfortunately the distributed docs are for IB 6.0.
There does not seem to be any way to get the updated 7.0 documentation
without paying $50 for the Media Kit and then $200 for the server license
after 90 days. While these prices are not steep for developing with
Interbase, they are if one already has payed for the $400 BCB6 upgrade which
includes the server and 5 client licenses. Unfortunately I don't see any
other way to get updated documentation.

> > > Then why is there an INT64 type mentioned in the system tables as a data
> > > type but not as a data type for columns when creating tables ?
> >
> > You would use NUMERIC(18,0).  INT64 is probably for UDFs, but I
> > haven't looked.
> >
> > > BTW, do you know if Borland
> > > intends to update the 6.0 .pdf documentation set distributed with 6.5 to
> > > something more recent or better ?
> > >
> > The docs have been updated for IB 7.0.  I would not expect
> > documentation updates other than the "Release Notes" for minor releases.
>
> I  am working with IB 6.5 which came with a 5 user client-server license
> when I upgraded to BCB6. Unfortunately the distributed docs are for IB 6.0.
> There does not seem to be any way to get the updated 7.0 documentation
> without paying $50 for the Media Kit and then $200 for the server license
> after 90 days. While these prices are not steep for developing with
> Interbase, they are if one already has payed for the $400 BCB6 upgrade which
> includes the server and 5 client licenses. Unfortunately I don't see any
> other way to get updated documentation.

btw - you pay the $400 for the BCB6 upgrade, the IB is bonus developer
license and cannot be deployed, AFAIK.


--

With regards,

Martijn Tonies
InterBase Workbench - the developer tool for InterBase
http://www.upscene.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."

In article <3de3f3cd$1@newsgroups.borland.com>, eddielee@tropicsoft.com 
says...
> I  am working with IB 6.5 which came with a 5 user client-server license
> when I upgraded to BCB6. Unfortunately the distributed docs are for IB 6.0.

	The docs included are for IB 6.5 -- that is, the 6.0 docs plus the 
release notes for IB 6.5.  There is no "IB 6.5 documentation set," because 
there weren't that many changes (from an end-user point of view -- many 
things were changed internally) between IB 6.0 and IB 6.5.

> There does not seem to be any way to get the updated 7.0 documentation
> without paying $50 for the Media Kit and then $200 for the server license
> after 90 days.

	Um, actually the Media Kit is only $30 if you have a 6.0 license.  
This gets you PDF documentation.  Printed manuals are $25 a piece.  If you 
intend to keep using 6.5 then you don't need anything else (though I don't 
know why you'd want the IB 7 docs if you want to use 6.5 only).

	If you want IB 7, and are a 6.5 licensee, then you need the 
following:

o  Media kit upgrade ($30)
o  Server license upgrade ($130)
o  Probably user licenses (server license includes one user license; see 
http://delphi.weblogs.com/stories/storyReader$236 for other options)

> While these prices are not steep for developing with
> Interbase, they are if one already has payed for the $400 BCB6 upgrade which
> includes the server and 5 client licenses. Unfortunately I don't see any
> other way to get updated documentation.

	Again, you already have the IB 6.5 documentation.  IMHO the 7.0 
documentation is mostly useful if you have IB 7.

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer

"Martijn Tonies" <m.tonies@upscene_remove.com> wrote in message
news:3de4c688@newsgroups.borland.com...
> > > > Then why is there an INT64 type mentioned in the system tables as a
data
> > > > type but not as a data type for columns when creating tables ?
> > >
> > > You would use NUMERIC(18,0).  INT64 is probably for UDFs, but I
> > > haven't looked.
> > >
> > > > BTW, do you know if Borland
> > > > intends to update the 6.0 .pdf documentation set distributed with
6.5 to
> > > > something more recent or better ?
> > > >
> > > The docs have been updated for IB 7.0.  I would not expect
> > > documentation updates other than the "Release Notes" for minor
releases.
> >
> > I  am working with IB 6.5 which came with a 5 user client-server license
> > when I upgraded to BCB6. Unfortunately the distributed docs are for IB
6.0.
> > There does not seem to be any way to get the updated 7.0 documentation
> > without paying $50 for the Media Kit and then $200 for the server
license
> > after 90 days. While these prices are not steep for developing with
> > Interbase, they are if one already has payed for the $400 BCB6 upgrade
which
> > includes the server and 5 client licenses. Unfortunately I don't see any
> > other way to get updated documentation.
>
> btw - you pay the $400 for the BCB6 upgrade, the IB is bonus developer
> license and cannot be deployed, AFAIK.

I don't need a deployment license, just the ability to develop. My ISP has
deployment licenses offered as part of my monthly payment.

>
>
> --
>
> With regards,
>
> Martijn Tonies
> InterBase Workbench - the developer tool for InterBase
> http://www.upscene.com
>
> Upscene Productions
> http://www.upscene.com
>
> "This is an object-oriented system.
> If we change anything, the users object."
>
>

"Craig Stuntz [TeamB]" <cstuntz@nospamplease.com (but use vertexsoftware to
email)> wrote in message
news:MPG.184ea0fc1b14d60798a288@newsgroups.borland.com...
> In article <3de3f3cd$1@newsgroups.borland.com>, eddielee@tropicsoft.com
> says...
> > I  am working with IB 6.5 which came with a 5 user client-server license
> > when I upgraded to BCB6. Unfortunately the distributed docs are for IB
6.0.
>
> The docs included are for IB 6.5 -- that is, the 6.0 docs plus the
> release notes for IB 6.5.  There is no "IB 6.5 documentation set," because
> there weren't that many changes (from an end-user point of view -- many
> things were changed internally) between IB 6.0 and IB 6.5.

Some of the docs are poor in places and, as I have posted on the
cppbuilder.documentation NG and on QC, actually missing some lines. I was
hoping that updated docs would be better and more complete.

>
> > There does not seem to be any way to get the updated 7.0 documentation
> > without paying $50 for the Media Kit and then $200 for the server
license
> > after 90 days.
>
> Um, actually the Media Kit is only $30 if you have a 6.0 license.
> This gets you PDF documentation.  Printed manuals are $25 a piece.  If you
> intend to keep using 6.5 then you don't need anything else (though I don't
> know why you'd want the IB 7 docs if you want to use 6.5 only).

See reason above. I suppose it is a futile hope to expect better docs for
7.0.

>
> If you want IB 7, and are a 6.5 licensee, then you need the
> following:
>
> o  Media kit upgrade ($30)
> o  Server license upgrade ($130)

I looked on the Interbase site and it didn't mention any upgrade prices.
Maybe I missed it.

In article <3de4fc52$1@newsgroups.borland.com>, eddielee@tropicsoft.com 
says...
> 
> Some of the docs are poor in places and, as I have posted on the
> cppbuilder.documentation NG and on QC, actually missing some lines. I was
> hoping that updated docs would be better and more complete.

	Again, there was no documentation update for 6.5.  The docs were 
updated for 7.
 
> See reason above. I suppose it is a futile hope to expect better docs for
> 7.0.

	Why?  The single report you made in QC is fixed in the IB 7 docs.  I 
can't comment on the other issues without knowing what they are.

> I looked on the Interbase site and it didn't mention any upgrade prices.
> Maybe I missed it.

	See the link I gave you; it's much easier to read than the Borland 
shop site.

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer

In article <MPG.184ecea32d02bcc598a296@newsgroups.borland.com>, 
cstuntz@nospamplease.com says...
> 	Again, there was no documentation update for 6.5. 
> 
	...other than the Release Notes.

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer

"Craig Stuntz [TeamB]" <cstuntz@nospamplease.com (but use vertexsoftware to
email)> wrote in message
news:MPG.184ed109402fc68998a297@newsgroups.borland.com...
> In article <MPG.184ecea32d02bcc598a296@newsgroups.borland.com>,
> cstuntz@nospamplease.com says...
> > Again, there was no documentation update for 6.5.
> >
> ...other than the Release Notes.

I was just looking for better docs, whether for 6.0, 6.5, 7.0, or whatever.
If it means getting the Media kit for 7.0, since it is a $30 upgrade, I will
consider it.

You are right that I only reported 1 doc problem on QC. While the docs for
Interbase are often decent, I found myself asking many questions which were
not explained for me fully in the docs but which your help and others, Jeff
Overcash especially, on the Interbase NGs have been able to resolve. The
support on the Interbase NGs is superb. It is an old story with Borland: if
the docs were better, than less people would need help on the NGs. That
doesn't make the help offered here any less valuable.

I could write up QC reports for better Interbase docs in the areas in which
I have found the .pdf files distributed with 6.5 insufficient, but then I
would never get any work done and the 7.0 docs may have already addressed my
concerns.

In article <3de51343$1@newsgroups.borland.com>, eddielee@tropicsoft.com 
says...
> I was just looking for better docs, whether for 6.0, 6.5, 7.0, or whatever.
> If it means getting the Media kit for 7.0, since it is a $30 upgrade, I will
> consider it.

	If there's a particular area you find lacking, I'll be happy to look 
and see if it's improved in the 7.0 docs before you buy.

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer

"Craig Stuntz [TeamB]" <cstuntz@nospamplease.com (but use vertexsoftware to
email)> wrote in message
news:MPG.184ee737a0b847f998a29b@newsgroups.borland.com...
> In article <3de51343$1@newsgroups.borland.com>, eddielee@tropicsoft.com
> says...
> > I was just looking for better docs, whether for 6.0, 6.5, 7.0, or
whatever.
> > If it means getting the Media kit for 7.0, since it is a $30 upgrade, I
will
> > consider it.
>
> If there's a particular area you find lacking, I'll be happy to look
> and see if it's improved in the 7.0 docs before you buy.

OK, I will report what I consider poor documentation here, if you like.
There doesn't seem to be a NG regarding Interbase docs, so I had reported a
previous documentation error on the cppbuilder.documentation NG as well as
QC.

In article <3de55403$1@newsgroups.borland.com>, eddielee@tropicsoft.com 
says...
> OK, I will report what I consider poor documentation here, if you like.
> 
	"Reports" (i.e., items needing to be fixed) should go in QC.  The 
best place to post documentation issues (to see if they've been fixed in 7 
already or need to go into QC) would be b.p.i.general.

	Thanks,

	-Craig

-- 
Craig Stuntz [TeamB] � Vertex Systems Corp. � Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase Perf. Monitor : http://delphi.weblogs.com/IBPerformanceMonitor
InterBase PLANalyzer 1.1: http://delphi.weblogs.com/IBPLANalyzer