"jose isaias cabrera" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> The PM is the same for the same ProjID because the split is a one to
> one
> assignment, so that should not happen. So, if there is a case like
> this,
> the PM has been set wrong. What I would like to have is a
"Igor Tandetnik" wrote...
> "jose isaias cabrera" <[EMAIL PROTECTED]>
> wrote in message news:[EMAIL PROTECTED]
>> imagine almost the same data,
>>
>> Class|ProjID|ProjFund|Invoice|PM|Split
>> Finishers|1045|73||JIC|
>> Finishers|1045|75|30|LED|
>> Finishers|1045|75|30|SAN|
>>
Hi José,
> I have one more ask for help, imagine almost the same data,
>
> Class|ProjID|ProjFund|Invoice|PM|Split
> Finishers|1045|73||JIC|
> Finishers|1045|75|30|LED|
> Finishers|1045|75|30|SAN|
> Finishers|1045|75|30|JIC|
> Finishers|1045|75||ELI|
> Finishers|1045|75|75|ELI|y
>
"jose isaias cabrera" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> imagine almost the same data,
>
> Class|ProjID|ProjFund|Invoice|PM|Split
> Finishers|1045|73||JIC|
> Finishers|1045|75|30|LED|
> Finishers|1045|75|30|SAN|
> Finishers|1045|75|30|JIC|
> Finishers|1045|75||ELI|
>
Hi José,
>> The benefits of normalizing increase with the amount and/or
>> complexity of your data. Notice there are no case statements to get
>> what you want. You just start with the table you want (Split, in
>> this case) and join any needed related data, so SQLite only scans
>> the
"Igor Tandetnik" wrote...
> jose isaias cabrera wrote:
>> Greetings...
>>
>> I know that Puneet will get on my case about the obscurity of the
>> subject (just kidding), but I am trying to find out if I can do this:
>> Imagine this table and data...
>>
>> Class|ProjID|ProjFund|Invoice|Split
>>
Yes, but I want to do them in one shot. Igor's solution worked perfectly.
josé
- Original Message -
From: "P Kishor" <[EMAIL PROTECTED]>
To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org>
Sent: Monday, February 11, 2008 6:12 PM
Sub
"BareFeet" wrote...
> Hi Jose,
>
>> Class|ProjID|ProjFund|Invoice|Split
>> Finishers|1045|73||
>> Finishers|1045|75|30|
>> Finishers|1045|75|30|
>> Finishers|1045|75|30|
>> Finishers|1045|75||
>> Finishers|1045|75|75|y
>> Finishers|1045|75|25|
>> Finishers|1045|73||
>> Finishers|1045|73||
>>
Hi Jose,
> Class|ProjID|ProjFund|Invoice|Split
> Finishers|1045|73||
> Finishers|1045|75|30|
> Finishers|1045|75|30|
> Finishers|1045|75|30|
> Finishers|1045|75||
> Finishers|1045|75|75|y
> Finishers|1045|75|25|
> Finishers|1045|73||
> Finishers|1045|73||
> Finishers|1045|73||
>
jose isaias cabrera <[EMAIL PROTECTED]>
wrote:
> Greetings...
>
> I know that Puneet will get on my case about the obscurity of the
> subject (just kidding), but I am trying to find out if I can do this:
> Imagine this table and data...
>
> Class|ProjID|ProjFund|Invoice|Split
> Finishers|1045|73||
On 2/11/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
>
> Greetings...
>
> I know that Puneet will get on my case about the obscurity of the subject
> (just kidding), but I am trying to find out if I can do this: Imagine this
> table and data...
>
> Class|ProjID|ProjFund|Invoice|Split
>
Greetings...
I know that Puneet will get on my case about the obscurity of the subject
(just kidding), but I am trying to find out if I can do this: Imagine this
table and data...
Class|ProjID|ProjFund|Invoice|Split
Finishers|1045|73||
Finishers|1045|75|30|
Finishers|1045|75|30|
12 matches
Mail list logo