Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #381
Closed
Open
Issue created Feb 03, 2016 by André Anjos@andre.anjos💬Owner

[many] Inconsistence between contribution name and associated file max size on database

As it stands, contribution names may be up to 200 characters wide, but associated description, declaration and code filenames only 100. If a user sets a longish name for the contribution (say, with 100 characters), Django will not be able to encode the associated files because their name will superseed the maximum capacity on the database.

We should double the size of the filenames compared to the name. Or halve the first.

Assignee
Assign to
Time tracking