CODEWITHSUNDEEP
ruby-on-railsdatabaseurlrest
meow
meow

Reputation: 28164

is it bad form to have the colon in db and in the URL?

I am designing my namespace such that the id i am storing in the DB is

id -> "e:t:222"

where "e" represents the Event class, "t" represents the type

i am also expecting to use this id in my urls

url -> /events/t:222

Is there anything wrong with doing this?

Upvotes: 1

Views: 291

Answers (2)

Stephen Petschulat
Stephen Petschulat

Reputation: 1177

There is nothing wrong with doing this, you'll simply need to encode the URL properly. Most libraries with do this automatically for you.

In general though, if you care about your data you shouldn't let the application drive the data or database design. Exceptions to this are application centric databases that have no life outside of a single application nor do you expect to use the data anywhere else. In this case, you may want to stick with schemas and idioms that work best with your application.

Upvotes: 0

Pekka
Pekka

Reputation: 449415

Is there anything wrong with doing this?

Yes: The colon is a reserved character in URLs that has a special meaning, namely specifying the server port, in a URL.

Using it in other places in the URL is a bad idea.

You would need to URLEncode the colon in order to use it.

Upvotes: 1

Related Questions