Still haven't answered my visibility question - but figured out the brilliant bug I implemented which caused me to question things. I have a primary key defined as a Smallint and an associated generator. You've probably already know what's coming...
This table has a high amount of inserts/deletes. Which rapidly increments the generator...which results in overflow errors. So...note to self: Either use a generator-based primary key sized to accommodate the traffic, or don't use a generator - use a composite PK which is sufficiently unique. Adding a dedicated unique field for PK's may be elegant...but has issues for high traffic. Which I would have figured out if I'd thought it through...
--
Daniel
__._,_.___
Posted by: "Daniel Miller" <dmiller@amfes.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (1) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu there.
Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu there.
Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.
__,_._,___
No comments:
Post a Comment