prashanth nagaraj wrote:Thanks for the above replies. But also wanted some links on the examples as asked in question1. Request you to share the same
Daniel Gen Li wrote:@ Gerardo
My theory is that it shouldn't. Because what's the difference between reading two files when they're spearate and when they're together? aside from the fact that they don't appear to be separate filesystem?
Kaustubh G Sharma wrote:I think java is more original than C# and secondly it is an open source which makes is more popular and famous.
Daniel Gen Li wrote: how would I know I've reached the end of the contents of one file and direct the rest of the input somewhere else?
Daniel Gen Li wrote:Not a bad idea at all. I've done zipping before, but how exactly could I load the extracted content into memory and read them as files? Perhaps load them into a byte buffer? because I'm making a game and I don't want people to just change the images so I want to place them all into a big file that's hard to decipher. lol
Bill Karwin wrote:
Gerardo Tasistro wrote:A column is added that identifies the type and thus allows the foreign key to reference only one table and not many as is the case of one table per class.
Yes, that's the common way to employ polymorphic associations: add another column for the "type" of entity you're referencing. For example:
The problem is that you can't declare a foreign key constraint to enforce referential integrity for polymorphic associations.
Bill Karwin wrote:
But I can think of at least one antipattern that Hibernate is guilty of: Polymorphic Associations. This encourages developers to design tables where a foreign key can reference any of several parent tables. But to achieve this, you have to forgo using a foreign key constraint to enforce the references. That should be a red flag right there that Polymorphic Associations violates database design principles.
Gregg Bolinger wrote:I believe it's user preference. I learn better by writing the code. And in fact, I hate tools like JFormDesigner. Not because there is anything wrong with the tool, but because of what it does. Other folks love those kinds of tools. The best approach is to try it both ways and figure out what works best for you. You guys will continue to go back and forth until you realize this. There is no right way for everyone.
Jim Hoglund wrote:
Gerardo : I guess that's just Campbell's point; that a beginning programmer can't read Java.
Keep in mind that a beginner does not know initialization code from today's rainfall, or a panel
layout from a shoe-shine kit.
Campbell Ritchie wrote:I see what you mean, but what happens when something goes wrong with a layout and you can't understand the code?
I think this thread would sit better on our GUIs forum, so I shall move it.
Campbell Ritchie wrote:But if you don't write code by hand, you will never understand what is going on. Avoid such automated tools like the plague until you are much more experienced.
Gerardo Tasistro wrote: . . . I'd recommend you get an evaluation version of JFormDesigner for the GUI development and download FatJar to bundle and deploy your application as a JAR file. With those two it's as simple as it gets.