Hi all, Recently i faced a interview for java.. In the interview they have asked me to say the codes rule and to explain that how we can say that any database is RDBMS .. also can any one please help me that wht r the relevent question that were asked in the 1-2 years of experience... :roll:
Manash, If you have computer science background you might have read C.J.Date's book on RDBMS. If not buy a copy, it will be money well spent. It will give you a solid foundation in RDBMS theory. If you want to go deeper after reading the book, get a math book that explains relational and set theory.
I have been doing Java/J2EE stuff for past 4 years and one fine day I have been asked to work on an ERP. As a software engineer one should be ready to work/face any kind of technology which is relevant. I dont say you be a Java developer today, Oracle DBA tomorrow and a Unix Sys Admin the next day. But expecting a RDBMS question is quite natural.
yes, but expecting questions about database theory is not. I'd expect that in an interview for a database designer or someone hired to implement a new database engine. If all you have to do is use the beast I'd expect at most a question about something specific in the SQL syntax of the engine they're using IF knowledge of the specific product (rather than "must have experience using Java with databases") is a listed requirement. This question sounds to me another sign of the current trend to want people with 20 year experience in J2EE for entry level positions.
If u r a comp sci graduate u should know it. If you are not, take this chance, learn about code rules. also try to learn the basic 'theory' you would be expected to know about. Try to cover as much you can. It would help you in your next interview and also, would minimize the difference between you and some other comp grad! Tina
Alongwith being a good coder, try to be a good professional as well!
Originally posted by Jonathan Hendry: I think you mean Codd's Rules of what a database must support to be relational. That might help you with Google. [ September 17, 2003: Message edited by: Jonathan Hendry ]
I'm glad you cleared that one up. I had no idea what he was talking about. It wasn't a one time typo. He used "codes rule" twice. I kept thinking "what the hell is this guy talking about?" The fact that he didn't know about Codd is not as important as the fact that he couldn't communicate that he didn't know about Codd. This is another great example of why not to hire someone, regardless of tech skills, unless they can communicate effectively.