Transmission database now in a database

Hi all,

I wrote a post about this in the transmission database thread but it seems to have been missed. So this is kind of a double post. I'm learning databases at the moment and MySQL in particular. I've put the whole list into a database partly for my own practice but also in the hope that it may actually be useful as well as academic. You'll find it here:

http://letslewisham.org/trans/search_trans.php

So that's what I did over the bank holiday weekend. Any thoughts and feedback welcome. It's quite simple but then when you're a relative newbie like me what looks quite simple is actually not that easy to put together.

Cheers.

sweet, good work arup. will you maintain this too?

That's a damned good idea - I saw your post in the thread and it immediately reminded me that I had to update my entry, so spent a while doing that and forgot to comment.
Good work!

genius, I searched for 3 random and i came up!

I wish people would include BB spindle length more often. Would have helped me out a bit today.

Oh, and nice work! Good idea.

@Ved

Not really sure what to do next. I wanted to build something that was real rather than imaginary. So I'll just wait for your feedback and develop accordingly. No point putting icing on the cake if nobody likes it.

You could import Sheldon's numbers and create an estimated chain line app?

I wish people would include BB spindle length more often. Would have helped me out a bit today.

That is a bit daft really - kind of defeats the object of having a transmission database in the first place

Not really sure what to do next. I wanted to build something that was real rather than imaginary. So I'll just wait for your feedback and develop accordingly. No point putting icing on the cake if nobody likes it.

Port it to PostgreSQL ;-)

(In all seriousness, MySQL is pretty idiosyncratic - postgres is a better introduction to databases in general as it's closer in function to Oracle and the other "grown up" RDBMSs. If you're doing this as a learning exercise it'd be quite fun and probably not take more than a couple of hours.)

Port it to PostgreSQL ;-)

(In all seriousness, MySQL is pretty idiosyncratic - postgres is a better introduction to databases in general as it's closer in function to Oracle and the other "grown up" RDBMSs. If you're doing this as a learning exercise it'd be quite fun and probably not take more than a couple of hours.)

I love that that made negative sense to me – I literally lost some sense reading that. You just made me stupider. Which, in turn, made me less able to understand. Which in turn made me stupider. I now have the IQ of an 8 year old. Thank you. :)

Nice, very good work!

I like it, very good! Am getting old cliff shrubb frame out of loft at weekend, will be back here to start fathoming out what wheels I need for what I think (at least 10 years ago!) is a chorus bb and chorus chainset!

very good and neat. thanks
i used this to build my bikes and now is much easier to use

I wish people would include BB spindle length more often. Would have helped me out a bit today.

Oh, and nice work! Good idea.

That is a bit daft really - kind of defeats the object of having a transmission database in the first place

i totally agree with horatio, after having loads of bb length strife.
IMO bb length is absolutley crucial, loads of people just put "shimano bb" etc. when shimano bb axle lengths range from 107 to 122.5! the same can be applied to campagnolo, phil wood or stronglight etc.

basically i think that bb length is the object of the the transmission database :-) and its a real shame its not included more often..

and nice one arup!

i totally agree with horatio, after having loads of bb length strife.
IMO bb length is absolutley crucial, loads of people just put "shimano bb" etc. when shimano bb axle lengths range from 107 to 122.5! the same can be applied to campagnolo, phil wood or stronglight etc.

basically i think that bb length is the object of the the transmission database :-) and its a real shame its not included more often..

That's what I meant

Yup. Without BB spindle length you're basically saying: "I used some stuff that worked. Good luck!"

SELECT 'decent chainline'
FROM arups_db
WHERE len('my 2nd hand shitty hub') <> len('my crappy old bb')
GO

?!?

hahah!

I suppose if this is something that people might actually want to use then you'll need to be able to add stuff to it and also edit it. Not something I know how to do yet. But should be an interesting exercise. Haven't even added my own one yet!

@Steff. I think I'll stick with MySQL for the moment as I'm considering doing the certification at some point.

I haven't done MySQL stuff for years but if I remember correctly it's not really that hard to add stuff. But you can make it as tricky as you like, I guess some kind of filter / check thing could be a good idea to make sure correct date is added?

i totally agree with horatio, after having loads of bb length strife.
IMO bb length is absolutley crucial, loads of people just put "shimano bb" etc. when shimano bb axle lengths range from 107 to 122.5! the same can be applied to campagnolo, phil wood or stronglight etc.

basically i think that bb length is the object of the the transmission database :-) and its a real shame its not included more often..

Of course, it's not just spindle length that is needed, but type of taper as well, JIS is not the same as ISO...

^ you can guess from the BB make on most occasions.

What's bugging me is that it doesn't answer my question: will 111mm campag centaur give me a straight chainline with sugino 75 and gran compe?

It comes up in the database, but people are using the same length bb (111mm) with goldtecs and phils etc, when goldtecs have a 3 mm difference in chainline...

So is 111 better for goldtec's 45 mm or is it better with regular 42 mm (with sugino 75's)?

In other words, I think people have uploaded their transmission set-up to the database irrespective of whether their chainline is straight or not.

I suppose someone with the know-how could make a database around quantitative not qualitative info - basically a chainline calculator.
You put in your BB dimensions, chainset type, gauge, hub type, rear spacing and cog type, and then you get either a big green tick or a big red cross as the output.
Or if you need to choose a component, you'd put in what you have got, and the database would tell you what choices you can make from there.

Fucked if I'd know how to do that.

I'll knock one up on Excell