Closed (won't fix)
Project:
Drupal core
Version:
7.x-dev
Component:
node system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Dec 2006 at 15:55 UTC
Updated:
10 Sep 2009 at 13:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
Paul Natsuo Kishimoto commentedUnless this is breaking Drupal, I would argue it isn't critical. It seems to only be forcing you to write shorter titles... however, I support the idea.
Comment #2
hickory commentedThis seems to fix things for now:
I think this is pretty important, and it would be good to see it in Drupal 5.
Comment #3
Zen commented128:
This is a very long title. This is a very long title. This is a very long title. This is a very long title. This is a very long255:
This is a very long title. This is a very long title. This is a very long title. This is a very long title. This is a very long. This is a very long title. This is a very long title. This is a very long title. This is a very long title. This is a very lUsers who want longer titles can just create a custom title field. This should, IMO, be more than sufficient for mainstream users esp. considering that D6 is MySQL 4+.
@hickory: Please submit your changes in patch form. It will also need to include an update function.
Thanks,
-K
Comment #4
hickory commentedWhat's the disadvantage of making the field TEXT, rather than limiting to a 255-char VARCHAR?
Comment #5
Paul Natsuo Kishimoto commented@zen: I don't understand why Drupal 6 requiring MySQL 4 or greater affects this issue. If anything, TEXT is more portable (considering support for other DBMS is always a good thing). Node titles should just work; a user would be substantially annoyed at having to create custom fields simply to enter a 129-character title. 128, 256 and similar numbers are entirely arbitrary. While they may seem comfortable sizes for English titles, they may be annoyingly restrictive in other languages. Arbitrary-length strings with
TEXTwould remove this problem.@hickory: as far as I know, there isn't. Roll that patch!
Comment #6
Zen commented4.0+ provides Unicode support. It is my understanding that 255 characters will now be 255 characters in all languages.
As to why TEXT is bad, please google for CHAR vs. VARCHAR vs. TEXT comparisons, keeping in mind the current indices of the node table. By your reasoning, we shouldn't have VARCHAR at all in our databases, eh?
Thanks,
-K
Comment #7
killes@www.drop.org commentedMaking titles TEXT could affect theintendedport to Oracle:
http://www.oracle.com/technology/pub/articles/pedros-drupal.html
Comment #8
hickory commentedWhat I understand from the Oracle article linked above is that it would use CLOB fields for long text as much as possible. The field types are presumably backend-specific anyway, so that shouldn't be a problem.
Speed is the main issue, I think. It would be good if someone could benchmark the difference.
Comment #9
dmitrig01 commentedno patch...
Comment #10
hickory commentedWhere would a patch for this go now? node.install?
Comment #11
hickory commentedHere's a patch for node.schema. I'm not sure if I've defined the 'node_title_type' index properly.
Comment #12
ChrisKennedy commentedDuplicate of http://drupal.org/node/126229
Comment #13
hickory commentedReopening as the other patch only increased the title length to 255.
Comment #14
catchNeeds to be re-rolled for scheme api, for drupal 7.
Comment #15
catchActually I'm going to mark this to won't fix. This could hit performance a lot on sorts since text (I think) requires temporary tables on sort.
CCK and automatic node titles provides a way to get the same functionality in contrib. If a title is longer than 256 characters then it's not really a title imo.
Comment #16
hickory commented*Please* don't mark this as wontfix unless benchmarks have been run. There have been previous theoretical objections relating to speed, but no-one's actually shown that this is a real problem, so far. On the other hand, I have a site where a large percentage of the nodes have titles longer than 255 characters (scientific papers, mostly), so this *is* a real problem.
Comment #17
catchThis thread deals with temporary tables to disk in taxonomy module: http://drupal.org/node/171685 - where converting a BLOB/TEXT column to varchar 255 was proposed for similar reasons. Leaving it as patch needs work anyway.
Comment #18
catch255 characters is still plenty, you can't do indexed conditions or order by on text tables, which you need for node titles very often, so back to won't fix. EXPLAIN is better than benchmarks for this.
Comment #19
hickory commentedIn that case, what should the recommended workaround be for sites with node titles longer than 255 characters? Create a separate field to hold the full title and store a truncated version in node.title?
Comment #20
catchI think so yeah - worth looking at http://drupal.org/project/auto_nodetitle which lets you hide the title field completely and generate the contents using token.module