java-database

[kamsky]

---

OT:

Para nako it's not a standard practice siguro na mo-ingon ka ug memory is cheap or upgrade lang ta ug hardware kung maka-encounter na mga in-ana na scenario. I think practice pud ug programming efficiency na dili lang mag-agad sa mga external factors. Especially, kung maka-trabaho na siya ug sa industries na lisud or daghan bureacracy ang pag-upgrades sa hardware and software. If I where him practice optimizing sa mga codes and logics.

OT:
para nako ill deliver the software which is agreeable with the Service Level Agreement. In our industry people's time is much expensive than the machine. Stability and quality is the #1 -- solves the functionality and stable enough to run a business, efficiency next.

And in your solution it's not efficient either.

[eax]

OT:
para nako ill deliver the software which is agreeable with the Service Level Agreement. In our industry people's time is much expensive than the machine. Stability and quality is the #1 -- solves the functionality and stable enough to run a business, efficiency next.

And in your solution it's not efficient either.

OT :
I think it depend siguro which comes first kung business or efficiency. Asa man pud na nimo ibutang ang mga scenarios na mga OutOfMemory? I'm pointing here you should also consider mga in-ana na hitabo-a. Dili lang ka pataka ug butang then later on maka-encounter na mga problems/issues na which ma prevent na siya during development.

[kamsky]

OT :
I think it depend siguro which comes first kung business or efficiency. Asa man pud na nimo ibutang ang mga scenarios na mga OutOfMemory? I'm pointing here you should also consider mga in-ana na hitabo-a. Dili lang ka pataka ug butang then later on maka-encounter na mga problems/issues na which ma prevent na siya during development.

of course business. what's the purpose of making program? is it for efficiency? it's for making money, business, and whatever purpose of your program.

your application is not for showing-off that you are using XML.

OutOfMemory, if I say your data would not be above 100 mb, that's a consideration and that wouldnt happen to his project -- unless he will put some garbage and memory leaks. And the service level agreement is the instructor is pleased that his cebuano translation works -- it's not a requirement to use an XML. You have to balance efficiency and program that works.

[sogate]

Just make sure na dili ka maka-generate ug OutOfMemoryException.

Hi guys,

Yes ok pud kaayo for me bay eax nga tan-awon and i-consider nato ang possible instances and problems nga mo-occur or ma-encounter nato while still in the development stage since I am planning to completely develop this in the future and let this be fully functional. But as of now, since my project is still a prototype context-driven machine translation, OK na kaayo na nako nga mo-work lang ang project using the simplest way possible. Dili lang sa ko anang XML bay or others, aside from a text file, kay it still needs me to study further kay have not used those languages yet and no enough knowledge about it yet.

[sogate]

bay kamsky, have tried properties a little bit already but I think I can't use it for my project study for the following reasons:
1. in a properties file, you can only store:
a.) a key--i assume this is the english word to be translated; and
b.) a value--i assume this is the cebuano translation of an english key.
2. my project study needs the following in a database:
a.) a key--english word;
b.) part of speech--i.e. noun, pronoun, etc.;
c.) possible words related to the key(english word); and
d.) possible cebuano translation
Example:
Sample sentence: I deposit my money to the bank.
a.) a key -- bank
b.) POS -- noun
c.) related words -- deposit,money
d.) cebuano translation -- bangko
thus, bank here is not the bank as in river bank but an institution or something

[junkfactory]

of course business. what's the purpose of making program? is it for efficiency? it's for making money, business, and whatever purpose of your program.

your application is not for showing-off that you are using XML.

OutOfMemory, if I say your data would not be above 100 mb, that's a consideration and that wouldnt happen to his project -- unless he will put some garbage and memory leaks. And the service level agreement is the instructor is pleased that his cebuano translation works -- it's not a requirement to use an XML. You have to balance efficiency and program that works.

Para sa kani nga project, kung simple key-value pair ra ang istoryahan, then I agree nga dili kinahanglan ang XML ani. Pero kung if it is more than a key value pair, I would love to see creating a master-child properties file manipulation nga walay labad sa ulo.

SAX does not load the entire document into memory, event handlers are used to avoid this. Ang properties file kaha, wala diay gi load sa memory? Looya

[kamsky]

interesting... let me check that later when i am at home. I think you need more complex object model then.

I am coding right now in a Bank

bay kamsky, have tried properties a little bit already but I think I can't use it for my project study for the following reasons:
1. in a properties file, you can only store:
a.) a key--i assume this is the english word to be translated; and
b.) a value--i assume this is the cebuano translation of an english key.
2. my project study needs the following in a database:
a.) a key--english word;
b.) part of speech--i.e. noun, pronoun, etc.;
c.) possible words related to the key(english word); and
d.) possible cebuano translation
Example:
Sample sentence: I deposit my money to the bank.
a.) a key -- bank
b.) POS -- noun
c.) related words -- deposit,money
d.) cebuano translation -- bangko
thus, bank here is not the bank as in river bank but an institution or something

[kamsky]

whats your input to lookup the database? Is it just a word 'bank'? in your example, 'bank' is not a key then because it can have multiple occurrences.

bay kamsky, have tried properties a little bit already but I think I can't use it for my project study for the following reasons:
1. in a properties file, you can only store:
a.) a key--i assume this is the english word to be translated; and
b.) a value--i assume this is the cebuano translation of an english key.
2. my project study needs the following in a database:
a.) a key--english word;
b.) part of speech--i.e. noun, pronoun, etc.;
c.) possible words related to the key(english word); and
d.) possible cebuano translation
Example:
Sample sentence: I deposit my money to the bank.
a.) a key -- bank
b.) POS -- noun
c.) related words -- deposit,money
d.) cebuano translation -- bangko
thus, bank here is not the bank as in river bank but an institution or something

[eax]

Murag lisud kung naa na mga relationships. Murag dili na madala ug file-based alone. Try na lang research/study ani Apache Lucene - Overview.

[sogate]

whats your input to lookup the database? Is it just a word 'bank'? in your example, 'bank' is not a key then because it can have multiple occurrences.

actually, the input is an english phrase/sentence and will be translated into a cebuano phrase/sentence, like: I deposit my money in the bank. (input), then the output would be Akong gideposito ang kwarta sa bangko.

The previous example was just to point out that the machine will translate a word in a phrase/sentence according to the related words that surround it (within a sentence).