 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Bear Guest
|
Posted: Sat Apr 22, 2006 5:03 am Post subject: How about poAutoRefresh flag in Delphi 2006 |
|
|
Bug: poAutoRefresh doesn't work
http://qc.borland.com/wc/qcmain.aspx?d=1585
It was closed at "Won't Do".
What does it mean?
Was it fixed in Delphi 2006 ?
Thanks.
Bear |
|
| Back to top |
|
 |
Bear Guest
|
Posted: Sat Apr 22, 2006 6:03 am Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Hi ,
if poAutoRefresh is not implemented it should allow the programmer set the
value of
TAutoIncField manually. But TAutoIncField's value is readonly!
Bear
"Bear" <bear (AT) nobody (DOT) com> 写入消息新闻:4449b522 (AT) newsgroups (DOT) borland.com...
|
|
| Back to top |
|
 |
Dan Miser Guest
|
Posted: Tue Apr 25, 2006 5:03 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
http://bdn.borland.com/article/0,1410,20847,00.html
--
Dan Miser
http://www.distribucon.com
"Bear" <bear (AT) nobody (DOT) com> wrote in message
news:4449b7b6 (AT) newsgroups (DOT) borland.com...
| Quote: | if poAutoRefresh is not implemented it should allow the programmer set
the value of
TAutoIncField manually. But TAutoIncField's value is readonly! |
|
|
| Back to top |
|
 |
Bear Guest
|
Posted: Thu Apr 27, 2006 1:03 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Thank you Dan Miser.
I knew this article.
but I think poAutoRefresh is more natural because sometimes we do not know
which filed is autoinc field.
You helped me a lot several years ago.
Best wishes to you.:)
Bear
"Dan Miser" <dmiser (AT) wi (DOT) rr.com> 写入消息新闻:444e4930$1 (AT) newsgroups (DOT) borland.com...
| Quote: | http://bdn.borland.com/article/0,1410,20847,00.html
--
Dan Miser
http://www.distribucon.com
"Bear" <bear (AT) nobody (DOT) com> wrote in message
news:4449b7b6 (AT) newsgroups (DOT) borland.com...
if poAutoRefresh is not implemented it should allow the programmer set
the value of
TAutoIncField manually. But TAutoIncField's value is readonly!
|
|
|
| Back to top |
|
 |
Bear Guest
|
Posted: Thu Apr 27, 2006 1:03 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
I will test it by myself.
Bear
"Dan Miser" <dmiser (AT) wi (DOT) rr.com> 写入消息新闻:444e4930$1 (AT) newsgroups (DOT) borland.com...
| Quote: | http://bdn.borland.com/article/0,1410,20847,00.html
--
Dan Miser
http://www.distribucon.com
"Bear" <bear (AT) nobody (DOT) com> wrote in message
news:4449b7b6 (AT) newsgroups (DOT) borland.com...
if poAutoRefresh is not implemented it should allow the programmer set
the value of
TAutoIncField manually. But TAutoIncField's value is readonly!
|
|
|
| Back to top |
|
 |
Dan Miser Guest
|
Posted: Thu May 04, 2006 6:14 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Good to hear. poAutoRefresh is still not implemented, and I'm having a hard
time figuring out if that will ever happen. Until then, that article should
be good enough for now.
--
Dan Miser
http://www.distribucon.com
"Bear" <bear (AT) nobody (DOT) com> wrote in message
news:4450ba8b (AT) newsgroups (DOT) borland.com...
| Quote: | Thank you Dan Miser.
I knew this article.
but I think poAutoRefresh is more natural because sometimes we do not know
which filed is autoinc field. |
|
|
| Back to top |
|
 |
Bear Guest
|
Posted: Fri May 05, 2006 4:14 am Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
yes. I did not find "AutoRefresh" in implementation section in Provider.pas
with Delphi 2006 Update1.
If it is possible it is better not to use AutoInc field, just use an AutoInc
table(and stored procedure, table fields : IDName, IDValue) to get the ID
value manually before inserting record.
Bear
"Dan Miser" <dmiser (AT) wi (DOT) rr.com> 写入消息新闻:445a3cab (AT) newsgroups (DOT) borland.com...
| Quote: | Good to hear. poAutoRefresh is still not implemented, and I'm having a
hard time figuring out if that will ever happen. Until then, that article
should be good enough for now.
--
Dan Miser
http://www.distribucon.com
"Bear" <bear (AT) nobody (DOT) com> wrote in message
news:4450ba8b (AT) newsgroups (DOT) borland.com...
Thank you Dan Miser.
I knew this article.
but I think poAutoRefresh is more natural because sometimes we do not
know which filed is autoinc field.
|
|
|
| Back to top |
|
 |
Ralf Jansen Guest
|
Posted: Fri May 05, 2006 9:14 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Bear schrieb:
| Quote: | ..
If it is possible it is better not to use AutoInc field, just use an AutoInc
table(and stored procedure, table fields : IDName, IDValue) to get the ID
value manually before inserting record.
|
Before implementing this you should consider using GUID's as PrimaryKeys.
You will get rid of all the refreshing issues you will face when using database generated ID's.
Ralf |
|
| Back to top |
|
 |
Erick Sasse Guest
|
Posted: Sat May 06, 2006 1:14 am Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Ralf Jansen wrote:
| Quote: | Before implementing this you should consider using GUID's as
PrimaryKeys.
|
I started using GUIDs as PK in a new project. I'm very happy with it.
Much easier to work than other approachs.
--
Erick Sasse
Brazil |
|
| Back to top |
|
 |
Bear Guest
|
Posted: Sat May 06, 2006 8:14 am Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
GUID as PK is good for some projects, but sometimes it is not good because:
1. PK is a long string not a Integer, it is slower to find the record by
GUID if there are a lot records.
2. It is too long to remember or print, for example, ClientID, an Integer
(example: 1003 ) is better than a GUID.
Bear
"Ralf Jansen" <Ralf.Jansen (AT) Schoenmackers (DOT) de>
??????:445b88dc$1 (AT) newsgroups (DOT) borland.com...
| Quote: |
Bear schrieb:
.. If it is possible it is better not to use AutoInc field, just use an
AutoInc table(and stored procedure, table fields : IDName, IDValue) to
get the ID value manually before inserting record.
Before implementing this you should consider using GUID's as PrimaryKeys.
You will get rid of all the refreshing issues you will face when using
database generated ID's.
Ralf |
|
|
| Back to top |
|
 |
Ralf Jansen Guest
|
Posted: Sat May 06, 2006 1:14 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Bear schrieb:
| Quote: | GUID as PK is good for some projects, but sometimes it is not good because:
1. PK is a long string not a Integer, it is slower to find the record by
GUID if there are a lot records.
|
Most DB's have a native GUID datatype nowadays. My personal experience is that there is no real
difference in performance between bigints and GUID's (measurable ok but not noticable from a users
perspective). If your DB doesn't support GUID's then implementing them as a string datatype may be a
problem.
| Quote: | 2. It is too long to remember or print, for example, ClientID, an Integer
(example: 1003 ) is better than a GUID.
Bear
|
In a well designed system you don't have the need for remembering(printing) them.
Ralf |
|
| Back to top |
|
 |
Erick Sasse Guest
|
Posted: Sat May 06, 2006 2:14 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Bear wrote:
| Quote: | 1. PK is a long string not a Integer, it is slower to find the record
by GUID if there are a lot records.
|
I agree with Ralf said. With the computer power we have today, there is
no noticeable difference.
| Quote: | 2. It is too long to remember or
print, for example, ClientID, an Integer (example: 1003 ) is better
than a GUID.
|
I never need to remember an ID and the user never sees it. If there is
a requirement to have an ID available to the user, I think it shouldn't
be the PK. In my recent projects, the PK is never shown to the users.
--
Erick Sasse
Brazil |
|
| Back to top |
|
 |
Bear Guest
|
Posted: Sat May 06, 2006 4:14 pm Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
Thanks for your ideas, Ralf and Erick.
:)
Bear
"Bear" <bear (AT) nobody (DOT) com> 写入消息新闻:445c596e (AT) newsgroups (DOT) borland.com...
| Quote: | GUID as PK is good for some projects, but sometimes it is not good
because:
1. PK is a long string not a Integer, it is slower to find the record by
GUID if there are a lot records.
2. It is too long to remember or print, for example, ClientID, an Integer
(example: 1003 ) is better than a GUID.
Bear
"Ralf Jansen" <Ralf.Jansen (AT) Schoenmackers (DOT) de
??????:445b88dc$1 (AT) newsgroups (DOT) borland.com...
Bear schrieb:
.. If it is possible it is better not to use AutoInc field, just use an
AutoInc table(and stored procedure, table fields : IDName, IDValue) to
get the ID value manually before inserting record.
Before implementing this you should consider using GUID's as PrimaryKeys.
You will get rid of all the refreshing issues you will face when using
database generated ID's.
Ralf
|
|
|
| Back to top |
|
 |
Tony Blomfield Guest
|
Posted: Wed May 17, 2006 11:14 am Post subject: Re: How about poAutoRefresh flag in Delphi 2006 |
|
|
IMO, GUID is an unaceptable solution.
1. It is slow.
2. Try brosiing a table full of Guids. Makes me go Dizzy, and its a
nightmare for support people.
Tony
"Ralf Jansen" <Ralf.Jansen (AT) Schoenmackers (DOT) de> wrote in message
news:445c9a76 (AT) newsgroups (DOT) borland.com...
| Quote: | Bear schrieb:
GUID as PK is good for some projects, but sometimes it is not good
because:
1. PK is a long string not a Integer, it is slower to find the record by
GUID if there are a lot records.
Most DB's have a native GUID datatype nowadays. My personal experience is
that there is no real
difference in performance between bigints and GUID's (measurable ok but
not noticable from a users
perspective). If your DB doesn't support GUID's then implementing them as
a string datatype may be a
problem.
2. It is too long to remember or print, for example, ClientID, an
Integer
(example: 1003 ) is better than a GUID.
Bear
In a well designed system you don't have the need for
remembering(printing) them.
Ralf |
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|