[help] [img] [forum]
[Catalog] · [Search] [News] [Manage]
[Return]
Posting mode: Reply
Post reply
Name
Email
Subject
Message
CAPTCHA CAPTCHA Challenge Click to refresh.
File
Password For post deletion.
Submit  
  • Helpful information is available in the visitor guide. Currently 11 unique user posts.
  • Supported file types are JPG, PNG and GIF.
  • Maximum file size allowed is 2MB.
  • Images greater than 250x250 will be thumbnailed.
  • Supported BBCode tags are b, code, i, pre, sjis, spoiler, s and u.
Sup, I remember reading about sriracha about two years ago and how it replaced per-board post numbers with a single global post count.

How difficult would it be to recreate more standard imageboard behavior?
Postnums are used in DB and in all other parts of the code, so not sure if this is even possible without some kind refactor


>>41(OP)
While the alternative is not entirely difficult to implement, I chose a single auto-increment ID for a few reasons. PostgreSQL does not natively support multi-column auto-increment IDs, any table and queries referencing a post would need to reference two columns instead of one, and moving threads between boards would require renumbering posts. Using a single post table with a single ID column greatly simplifies the application and the database schema. I understand the alternative is desirable for imageboards, and things may change in the future, but right now I don't see the performance and complexity costs as worth it.

Delete Post  
- Sriracha -