Databases
StackOverflow2013
Postsdbo
PODjango, accessing PostgreSQL sequence
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango, accessing PostgreSQL sequence
    primarykey
    data
    text
    <p>In a Django application I need to create an order number which looks like: yyyymmddnnnn in which yyyy=year, mm=month, dd=day and nnnn is a number between 1 and 9999.</p> <p>I thought I could use a PostgreSQL sequence since the generated numbers are atomic, so I can be sure when the process gets a number that number is unique.</p> <p>So I created a PostgreSQL sequence:</p> <pre><code>CREATE SEQUENCE order_number_seq INCREMENT 1 MINVALUE 1 MAXVALUE 9999 START 1 CACHE 1 CYCLE; </code></pre> <p>This sequence can be accessed as a tables having one row. So in the file checkout.py I created a Django model to access this sequence.</p> <pre><code>class OrderNumberSeq(models.Model): """ This class maps to OrderNumberSeq which is a PostgreSQL sequence. This sequence runs from 1 to 9999 after which it restarts (cycles) at 1. A sequence is basically a special single row table. """ sequence_name = models.CharField(max_length=128, primary_key=True) last_value = models.IntegerField() increment_by = models.IntegerField() max_value = models.IntegerField() min_value = models.IntegerField() cache_value = models.IntegerField() log_cnt = models.IntegerField() is_cycled = models.BooleanField() is_called = models.BooleanField() class Meta: db_table = u'order_number_seq' </code></pre> <p>I set the sequence_name as primary key as Django insists on having a primary key in a table.</p> <p>The I created a file get_order_number.py with the contents:</p> <pre><code>def get_new_order_number(): order_number = OrderNumberSeq.objects.raw("select sequence_name, nextval('order_number_seq') from order_number_seq")[0] today = datetime.date.today() year = u'%4s' % today.year month = u'%02i' % today.month day = u'%02i' % today.day new_number = u'%04i' % order_number.nextval return year+month+day+new_number </code></pre> <p>now when I call 'get_new_order_number()' from the django interactive shell it behaves as expected.</p> <pre><code>&gt;&gt;&gt; checkout.order_number.get_new_order_number() u'201007310047' &gt;&gt;&gt; checkout.order_number.get_new_order_number() u'201007310048' &gt;&gt;&gt; checkout.order_number.get_new_order_number() u'201007310049' </code></pre> <p>You see the numbers nicely incrementing by one every time the function is called. You can start multiple interactive django sessions and the numbers increment nicely with no identical numbers appearing in the different sessions.</p> <p>Now I try to use call this function from a view as follows:</p> <pre><code>import get_order_number order_number = get_order_number.get_new_order_number() </code></pre> <p>and it gives me a number. However next time I access the view, it increments the number by 2. I have no idea where the problem is.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USHenri
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango, accessing PostgreSQL sequence
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango, accessing PostgreSQL sequence
      1. USAlexandr
      1. VTFavorite
    1. COI think we need to see more from your view code.
      singulars
      1. PODjango, accessing PostgreSQL sequence
      1. USKillianDS
    2. COBasically there's not much more in the view code. But I have changed my mind on how to generate order numbers anyhow. I needed to generate unique order numbers to be able to track orders if necessary. And the way I tried, has a serious drawback. I have to reset the counter every day at exactly midnight. Anyway all you guys thanks for responding.
      singulars
      1. PODjango, accessing PostgreSQL sequence
      1. USHenri
    3. COIt appeared the error was in another part of the application, so the problem is solved. Somewhere I read something about generating order numbers: http://stackoverflow.com/questions/1179439/best-way-to-generate-order-numbers-for-an-online-store and here are some very useful tips.
      singulars
      1. PODjango, accessing PostgreSQL sequence
      1. USHenri
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload