primary-key

Is there a way to reset the primary key of a PostgreSQL table to start at 1 again on a populated table? Right now it's generating numbers from 1000000 and up. I want it all to reset and start to 1, keeping all my existing data intact. Primary keys that autoincrement (i.e., columns with data type serial primary key ) are associated with a sequence . You can set the next value for any sequence using the setval(<seqname>, <next_value>) function. Note that to actually execute the function by itself you need to use SELECT , like this: SELECT setval(<seqname>, <next_value>) The name of the auto

I am not able to understand what Range primary key is here - http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#WorkingWithTables.primary.key and how does it work? What do they mean by "unordered hash index on the hash attribute and a sorted range index on the range attribute"? mkobit " Hash and Range Primary Key " means that a single row in DynamoDB has a unique primary key made up of both the hash and the range key. For example with a hash key of X and range key of Y , your primary key is effectively XY . You can also have multiple range keys for the same

How do I just print out a 'primary key' for the column with the primary key? I get 'primary key' for all the columns if the table has a primary key, instead of the one column with the primary key and the other columns as blank in keyType. SELECT c.TABLE_NAME, c.COLUMN_NAME, c.DATA_TYPE, c.Column_default, c.character_maximum_length, c.numeric_precision, c.is_nullable, CASE WHEN u.CONSTRAINT_TYPE = 'PRIMARY KEY' THEN 'primary key' ELSE '' END AS KeyType FROM INFORMATION_SCHEMA.COLUMNS as c LEFT JOIN information_schema.table_constraints as u ON c.table_name = u.table_name ORDER BY table_name

I am in the process of re-writing an MS Access database to SQL server and have found an strange issue in Access that I am hoping someone can help with. I have a table let's call it 'Main' with a Primary Key on the Account that is indexed and doesn't allow for duplicates. Seems simple enough but my issue is occurring when data is getting Inserted. My INSERT query is (the number of fields have been limited for brevity) INSERT INTO Main (Account, SentDate, Amount) SELECT C.Account, C.SentDate, C.Amount FROM (CALLS C LEFT JOIN Bals B ON C.Account = B.ACCT_ID) LEFT JOIN AggAnt A ON C.Account = A

I would like to create a bigint (or string or whatever that is not int ) typed primary key field under Rails 3. I have a given structure of data, for example: things ------ id bigint primary_key name char(32) The approach I'm currently trying to push: create_table :things, :id => false do |t| # That prevents the creation of (id int) PK t.integer :id, :limit => 8 # That makes the column type bigint t.string :name, :limit => 32 t.primary_key :id # This is perfectly ignored :-( end The column type will be correct, but the primary key option will not be present with sqlite3 and I suspect that this

I have a ReferenceID varchar(6) column in over 80 different tables. I need to extend this to a varchar(8) throughout the db following a change implemented by the government organisation that assigns the IDs. I was hoping to declare a cursor to get the table names as follows: DECLARE @TableName AS VARCHAR(200) DECLARE TableCursor CURSOR LOCAL READ_ONLY FOR SELECT t.name AS TableName FROM sys.columns c JOIN sys.tables t ON c.object_id = t.object_id WHERE c.name = 'ReferenceID' OPEN TableCursor FETCH NEXT FROM TableCursor INTO @TableName and then edit the type as follows: ALTER TABLE @TableName

Let me quickly describe my problem. I have 5 databases for 5 customers and each has the same table called SubnetSettings . I already created a dropdownlist to select a customer and will shows up the SubnetSetting table which belong to selected customer and allow me to create, edit and delete. I can create, delete without problem but when I want to edit the data it brings the error: Server Error in '/TMS' Application. Attaching an entity of type 'CFS.Domain.Entities.SubnetSettings' failed because another entity of the same type already has the same primary key value. This can happen when using

Are there any repercussions using Negative Primary Keys for tables (Identity Increment -1, Identity Seed -1 in SQL Server 2005)? The reason for this is we're creating a new database to replace an existing one. There are similar tables between the two databases and we'd like the "source" of the information to be transparent to our applications. The approach is to create views that unions tables from both databases. Negative PKs ensures the identities don't overlap. Like others have said, the database is fine with this. But it would be a problems for a .NET application that uses DataSet