Re: What is the proper (least expensive) way to do this

RedRed!com IT Department wrote: So, for my peace of mind, I would need to follow these procedures to ensure Martijn's issue doesn't happen: 1. lock the table 2. execute my select 3. insert if it does not already exist 4. unlock the table On a high level, is this a correct list of procedure

Re: What is the proper (least expensive) way to do this

Martijn Tonies wrote: Connie, I have a database for ASN information in which I save asn information for reference by other scripts (asn lookup can be expensive). CREATE TABLE `ASNINFO` ( `asnInfoID` int(11) NOT NULL auto_increment, `asNumber` int(11) NOT NULL default '0', `description` va

Re: What is the proper (least expensive) way to do this

Connie, > I have a database for ASN information in which I save asn information for reference by other scripts (asn lookup can be expensive). > > CREATE TABLE `ASNINFO` ( > `asnInfoID` int(11) NOT NULL auto_increment, > `asNumber` int(11) NOT NULL default '0', > `description` varchar(255) default

What is the proper (least expensive) way to do this

I have a database for ASN information in which I save asn information for reference by other scripts (asn lookup can be expensive). CREATE TABLE `ASNINFO` ( `asnInfoID` int(11) NOT NULL auto_increment, `asNumber` int(11) NOT NULL default '0', `description` varchar(255) default NULL, `comment`